How to use Claude to document legacy game code
Wesner used Claude Code to document Micropolis, published the documents and prompt, and converted them into audio. Don Hopkins reviewed the documentation and praised specific coverage.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Read the entire [legacy repository] and write documentation covering its architecture, variants, notable features, and licensing statements. Ground each claim in repository evidence. Flag uncertainty for [maintainer] to review.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- DonHopkins
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Wesner reported apparently correct and complete documentation; Hopkins praised its coverage of versions, licensing, trademarks, and an Eliza easter egg.
- Human involvement
- Wesner checked the documentation; Don Hopkins also reviewed it and listened to the audio version.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Have Claude Code read the entire Micropolis codebase.
- Generate full documentation and publish it with the prompt.
- Convert the documentation into a podcast episode.
Fabian Wesner used Claude Code to document Micropolis, the open-source release of the original SimCity. He asked it to read the entire codebase and write full documentation, then published the resulting documents and the prompt in his repository. He also converted the documentation into a podcast episode for easier consumption. The supplied post mentions a JavaScript rebuild, but gives no implementation steps for that separate project.
Wesner said the documentation looked correct and complete, while acknowledging that he was not an expert on this particular codebase. Don Hopkins, who said he knew the code, reviewed the documentation and described specific things it covered. It mapped and compared different versions, caught an experimental Eliza chatbot easter egg in the PyGTK version, and addressed licensing and trademark issues. It also noted that active development had moved to MicropolisCore. Hopkins listened to the audio version and called it comprehensive and technically accurate, with a reservation about its closing city-planning claim.
Who it's for: Maintainers investigating unfamiliar legacy repositories who want documentation they can check against the code.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · DonHopkins
Frequently asked questions
What did Claude Code read?
Wesner said he let Claude Code read the entire Micropolis codebase and write full documentation.
Who checked the documentation?
Wesner assessed it as correct and complete without claiming codebase expertise. Don Hopkins reviewed it and praised its version mapping, licensing coverage, and discovery of an Eliza easter egg.
More details
Remaining steps
- Have a developer familiar with the code review the documentation.
About this account
Claude Code read the repository and generated documentation at the author’s request.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=47972162. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: DonHopkins on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Micropolis repository
Software development
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.