agentleFS
Sign inStart free
chuanglibschuanglibs/Claude-Code-Game-Studios-Codex/design/CLAUDE.md

Claude-Code-Game-Studios-Codex / design

CLAUDE.md1 starsChanged 59 days agoMITView on GitHub

When authoring or editing files in this directory, follow these standards. Every GDD must include all 8 required sections in this 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 File naming: [system-slug].md (e.g.…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this CLAUDE.md into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    When authoring or editing files in this directory, follow these standards.

    line 3
  2. Distinctive:

    Every GDD must include all 8 required sections in this order:

    line 7
  3. Very specific:

    Validation: Run /design-review [path] after authoring any GDD.

    line 23
  4. Very specific:

    Run /review-all-gdds after completing a set of related GDDs.

    line 24
  5. Very specific:

    Use /quick-design to author.

    line 29
  6. Very specific:

    Use /ux-design to author. Validate with /ux-review before passing to /team-ui.

    line 38

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Design Directory

When authoring or editing files in this directory, follow these standards.

GDD Files (design/gdd/)

Every GDD must include all 8 required sections in this 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

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/ux/accessibility-requirements.md

Use /ux-design to author. Validate with /ux-review before passing to /team-ui.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free