codex-game-studios / design
CLAUDE.md1 starsChanged 26 days agoMITView on GitHub
When authoring or editing files in this directory, follow these standards. The 8 GDD sections, in order: 1. Overview — one-paragraph summary 2. Player Fantasy — intended feeling and experience 3. Detailed Rules — unambiguous mechanics 4. Formulas — all math defined with variables 5. Edge Cases — unusual situations handled 6. Dependencies — other systems listed 7. Tuning Knobs — configurable values identified 8. Acceptance Criteria — testable success conditions How many are REQUIRED depends on modes.workflow — all…
1 other project uses a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- Donchitos/Claude-Code-Game-Studiosword for word, first seen Oct 19, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Donchitos/Claude-Code-Game-Studios★ 27k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CCGS Skill Testing Framework/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- asset-auditSkill
- asset-specSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- bug-triageSkill
- changelogSkill
- code-reviewSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- estimateSkill
- gate-checkSkill
- helpSkill
- hotfixSkill
- launch-checklistSkill
- localizeSkill
- map-systemsSkill
- milestone-reviewSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- playtest-reportSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- prototypeSkill
- qa-planSkill
- quick-designSkill
- regression-suiteSkill
- release-checklistSkill
- retrospectiveSkill
- reverse-documentSkill
- review-all-gddsSkill
- scope-checkSkill
- security-auditSkill
- settingsSkill
- setup-engineSkill
- skill-improveSkill
- skill-testSkill
- smoke-checkSkill
- soak-testSkill
- sprint-planSkill
- sprint-statusSkill
- startSkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 3
When authoring or editing files in this directory, follow these standards.
- Very specific: line 40
Validation: Run /design-review [path] after authoring any GDD.
- Very specific: line 41
Run /review-all-gdds after completing a set of related GDDs.
- Very specific: line 46
Use /quick-design to author.
- Very specific: line 55
Use /ux-design to author. Validate with /ux-review before passing to /team-ui.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design Directory
When authoring or editing files in this directory, follow these standards.
GDD Files (design/gdd/)
The 8 GDD sections, in order:
- Overview — one-paragraph summary
- Player Fantasy — intended feeling and experience
- Detailed Rules — unambiguous mechanics
- Formulas — all math defined with variables
- Edge Cases — unusual situations handled
- Dependencies — other systems listed
- Tuning Knobs — configurable values identified
- Acceptance Criteria — testable success conditions
How many are REQUIRED depends on modes.workflow — all 8 at full; 5 at
standard (Overview, Detailed Rules, Edge Cases, Dependencies, Acceptance
Criteria, plus Formulas when the system has math); none at minimal, where
design/game-brief.md is the design record instead of a GDD. Resolve the tier
before flagging a section as missing — see .claude/docs/workflow-modes.md.
Three other places already encode the tier rule —
.claude/docs/coding-standards.md,.claude/rules/design-docs.mdand.claude/hooks/validate-commit.sh. This file is the copy a session working indesign/reads first, so it must agree with them: demanding all 8 atminimalwarns a jam project about six sections its own configuration says it does not need, which trains the user to ignore the warning.
Section-name alias: the GDD template and /design-system author section 3
as ## Detailed Design; the standard calls it Detailed Rules. Same required
section — accept either heading, never rewrite one into the other.
File naming: [system-slug].md (e.g. movement-system.md, combat-system.md)
Systems index: design/gdd/systems-index.md — update when adding a new GDD.
Design order: Foundation → Core → Feature → Presentation → Polish
Validation: Run /design-review [path] after authoring any GDD.
Run /review-all-gdds after completing a set of related GDDs.
Quick Specs (design/quick-specs/)
Lightweight specs for tuning changes, minor mechanics, or balance adjustments.
Use /quick-design to author.
UX Specs (design/ux/)
- Per-screen specs:
design/ux/[screen-name].md - HUD design:
design/ux/hud.md - Interaction pattern library:
design/ux/interaction-patterns.md - Accessibility requirements:
design/accessibility-requirements.md
Use /ux-design to author. Validate with /ux-review before passing to /team-ui.
Accessibility requirements sit OUTSIDE
design/ux/on purpose. They are a project-wide standard the per-screen specs consult, not a spec for one screen..claude/docs/workflow-catalog.yaml, the Pre-Production, Production and Polish gates, and/architecture-reviewall checkdesign/accessibility-requirements.mdat that exact path. Do not "tidy" it underdesign/ux/— every one of those checks would stop matching, and the Technical Setup → Pre-Production gate would become unpassable./ux-designstates the same rule at itsaccessibilitymode.
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.