gdd
Skill9 starsChanged 7 months agoMITView on GitHub
Create or update a Game Design Document. Use for master GDD creation, system-specific GDDs, or GDD review. Invoke with /gdd [system-name] for a specific system, or /gdd for the master document.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- wxxb789/hoatheir own version, first seen Nov 16, 2026
- mementomori-co/maker-masterytheir own version, first seen Oct 25, 2026
- skealeye/ClaudeSkillstheir own version, first seen Oct 14, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- wxxb789/hoa★ 3same name
- mementomori-co/maker-mastery★ 2same name
- skealeye/ClaudeSkills★ 0same name
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
- 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
- reverse-documentSkill
- 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
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Create the master GDD at design/gdd/master-gdd.md using the template at .claude/docs/templates/gdd-master.md.
- Very specific: line 24
Create a system-specific GDD at design/gdd/<system-name>-gdd.md using the template at .claude/docs/templates/gdd-system.md.
- Distinctive: line 26
Every system GDD must include:
- Very specific: line 43
Update Index: If a new system, update design/gdd/systems-index.md
- Very specific: line 46
Run /design-review to validate quality
- Very specific: line 47
Update design/gdd/systems-index.md if a new system was added
“Common” is measured: kept by at least 6 in 10 of the 3 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
/gdd — Game Design Document Workflow
If no argument provided (Master GDD):
Create the master GDD at design/gdd/master-gdd.md using the template at .claude/docs/templates/gdd-master.md.
The master GDD must include:
- Game Overview: Concept, genre, platform (Roblox), target audience
- Creative Pillars: 3-5 pillars that guide all decisions
- Core Loop: 30-second, 5-minute, session, and meta loops
- Systems Overview: List all game systems with 1-sentence descriptions
- Player Progression: How do players grow over time?
- Monetization Strategy: GamePasses, DevProducts, Premium Benefits
- Social Features: Multiplayer, trading, guilds, parties
- Target Metrics: D1/D7/D30 retention targets, session length goals
- Content Plan: Launch content vs. future updates
- Technical Overview: Client-server split, DataStore approach, key technical constraints
If argument provided (System GDD):
Create a system-specific GDD at design/gdd/<system-name>-gdd.md using the template at .claude/docs/templates/gdd-system.md.
Every system GDD must include:
- Overview & Purpose
- Core Mechanics (detailed)
- Data Schema (DataStore keys, types, defaults)
- Client-Server Split (what runs where)
- RemoteEvents/Functions needed (with argument contracts)
- Player-Facing UI (mockup or description)
- Edge Cases & Error States
- Balancing Parameters (formulas, not magic numbers)
- Integration Points (dependencies on other systems)
Workflow Steps
- Ask Context: "Are you creating a new GDD or updating an existing one?"
- Delegate: Route to
game-designeragent for master GDD, orsystems-designerfor system GDD - Draft: Show the draft to the user for review (never save directly)
- Iterate: Apply feedback, present updated draft
- Approve: User confirms; save to
design/gdd/ - Update Index: If a new system, update
design/gdd/systems-index.md
After creating any GDD:
- Run
/design-reviewto validate quality - Update
design/gdd/systems-index.mdif a new system was added - Link related GDDs (combat GDD references weapons GDD, etc.)
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.

