reverse-document
Skill9 starsChanged 7 months agoMITView on GitHub
Generate design docs from existing code. Reverse-engineer GDDs from implementation when a project has code but no design docs.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
- scotidev/GameDevStudiotheir own version, first seen Oct 9, 2026
- HunLuanZhiZhu/Game-Studios-Plugintheir own version, first seen Oct 5, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dawn840705/codex-code-studios★ 17same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
- hongyuanc/codex-game-studios★ 5same name
- timjrobinson/Claude-Code-Construction-Manager★ 4same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 79
Ask them to fill in sections marked [NEEDS USER INPUT]
- Very specific: line 80
Ask them to correct any [INFERRED FROM CODE] that are wrong
- Distinctive: line 81
Look for discrepancies (code says X, user says Y — which is authoritative?)
- Very specific: line 86
Update or create design/gdd/systems-index.md
- Very specific: line 87
Create design/gdd/master-gdd.md if missing (may need user input for vision/pillars)
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/reverse-document — Reverse Engineering Design Docs
Delegate to: systems-designer (with lead-programmer for code analysis)
Use When
- Joining a project with no design documentation
- Code has diverged from original design docs
- Need to produce docs for handoff or publishing
- Preparing for
/design-reviewon an unfinished codebase
Steps
1. Scan the Codebase
Identify major systems by:
- Top-level directories in
src/ - Module names
- Service files
- Obvious feature clusters
ls src/ServerScriptService/
ls src/ServerStorage/
ls src/ReplicatedStorage/2. For Each System, Extract Info
Purpose (from code inspection)
- Module comments (if any)
- File names
- Public function names
- Type definitions
Data Schema
- Find DataStore keys
- Find config tables
- Find Attribute usage
- Find persistent state
grep -rn "DataStore\|Attribute\|ValueObject" src/Remotes
- Find RemoteEvents / RemoteFunctions created
- Find FireServer / FireClient / InvokeServer / InvokeClient
- Find OnServerEvent / OnClientEvent handlers
grep -rn "RemoteEvent\|RemoteFunction\|OnServerEvent\|OnClientEvent" src/Client-Server Split
- What files are in ServerScriptService vs. StarterPlayer?
- What's shared via ReplicatedStorage?
UI
- What ScreenGuis exist?
- What buttons/modals/HUDs?
- Sketch the structure
Formulas
- Find numeric operations in gameplay code
- Extract the math into explicit formulas
- Flag magic numbers that should be documented
3. Draft a GDD
For each system, generate a draft GDD using the template. Mark sections as:
[INFERRED FROM CODE]— extracted from implementation[NEEDS USER INPUT]— couldn't determine from code
4. Present for Review
Show each drafted GDD to the user:
- Ask them to fill in sections marked
[NEEDS USER INPUT] - Ask them to correct any
[INFERRED FROM CODE]that are wrong - Look for discrepancies (code says X, user says Y — which is authoritative?)
5. Save and Link
On approval:
- Save each GDD to
design/gdd/<system>-gdd.md - Update or create
design/gdd/systems-index.md - Create
design/gdd/master-gdd.mdif missing (may need user input for vision/pillars)
6. Flag Discrepancies
Note anywhere the code doesn't match what the user says the design should be:
- "Code implements X, but you said the design is Y — should we update the code or the design?"
- Log these in
production/decision-log.md
Output
# Reverse Documentation Results
## Systems Found
1. [System A] — GDD draft saved
2. [System B] — GDD draft needs user input for [sections]
## Discrepancies Found
1. [System X] — Code does Y, but that's not documented anywhere. Intentional?
## Missing Systems (code without doc)
1. [Module] — unclear what this is. User clarification needed.
## Docs Without Code (if master-gdd exists)
- [Planned system] — no code yet
## Recommendations
1. [Action item]Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

