codex-game-studios
CLAUDE.md1 starsChanged 26 days agoMITView on GitHub
Indie game development managed through 49 coordinated Claude Code subagents. Each agent owns a specific domain, enforcing separation of concerns and quality. Note: Engine-specialist agents exist for Godot, Unity, and Unreal with dedicated sub-specialists. Use the set matching your engine. @.claude/docs/directory-structure.md project.yaml at the repo root is the primary config store — engine, specialists, naming, platform, performance, modes. Skills resolve it via resolve_config (see .claude/docs/config-resolution.md). .claude/docs/technical-preferences.md is the legacy fallback, read on demand when a key is absent from project.yaml.…
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CCGS Skill Testing Framework/CLAUDE.mdCLAUDE.md
- design/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
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Every task follows: Question -> Options -> Decision -> Draft -> Approval
- Distinctive: line 57
No commits without user instruction
- Very specific: line 74
Read .claude/docs/context-management.md on demand — it is a reference, not session context.
≈ “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
Claude Code Game Studios -- Game Studio Agent Architecture
Indie game development managed through 49 coordinated Claude Code subagents. Each agent owns a specific domain, enforcing separation of concerns and quality.
Technology Stack
- Engine: [CHOOSE: Godot 4 / Unity / Unreal Engine 5]
- Language: [CHOOSE: GDScript / C# / C++ / Blueprint]
- Version Control: Git with trunk-based development
- Build System: [SPECIFY after choosing engine]
- Asset Pipeline: [SPECIFY after choosing engine]
Note: Engine-specialist agents exist for Godot, Unity, and Unreal with dedicated sub-specialists. Use the set matching your engine.
Project Structure
@.claude/docs/directory-structure.md
Engine Version Reference
<!-- ENGINE-REFERENCE-IMPORT: the line below is engine-specific. /setup-engine
rewrites it to @docs/engine-reference/<engine>/VERSION.md for the chosen
engine, so a Unity or Unreal project stops loading the Godot reference every
session. It defaults to Godot (the template's example engine); skills that
need the pinned version read docs/engine-reference/<engine>/VERSION.md on
demand regardless of this import. -->@docs/engine-reference/godot/VERSION.md
Technical Preferences
project.yaml at the repo root is the primary config store — engine, specialists,
naming, platform, performance, modes. Skills resolve it via resolve_config
(see .claude/docs/config-resolution.md).
.claude/docs/technical-preferences.md is the legacy fallback, read on demand
when a key is absent from project.yaml. It is no longer imported here: before
/setup-engine runs it is almost entirely [TO BE CONFIGURED] placeholders, and
after it runs project.yaml holds the real values.
Coordination Rules
@.claude/docs/coordination-rules.md
Collaboration Protocol
User-driven collaboration, not autonomous execution. Every task follows: Question -> Options -> Decision -> Draft -> Approval
- Agents MUST ask "May I write this to [filepath]?" before using Write/Edit tools
(exempt:
active.mdappends, agent memory, a subagent's new file at the path its orchestrating skill named; see.claude/rules/agent-memory.md) - Agents MUST show drafts or summaries before requesting approval
- Multi-file changes require explicit approval for the full changeset
- No commits without user instruction
- A skipped or dismissed question is not an answer: act on nothing, re-ask in plain text and wait
- Started outside this file's folder? Warn first: hooks, deny rules and the ask-first mode load only when Claude Code starts here
See docs/COLLABORATIVE-DESIGN-PRINCIPLE.md for full protocol and examples.
First session? If the project has no engine configured and no game concept, run
/startto begin the guided onboarding flow.
Coding Standards
@.claude/docs/coding-standards.md
Context Management
Read .claude/docs/context-management.md on demand — it is a reference, not
session context. Two of its conventions are load-bearing and cited by name
elsewhere in the repo, so they are restated here rather than lost:
production/session-state/active.mdis the session checkpoint. The file is the memory, not the conversation. Read it first after any compaction, crash, or/clear.- Helpers in
.claude/scripts/emit observations, never verdicts. A script that scores or judges will eventually contradict a mode or override it cannot see. (Cited byartifact-check.shandadr-dep-graph.sh.)
Project Notes
Project-specific rules, shared with Codex. Where they conflict with the defaults above, they win.
@PROJECT-NOTES.md
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.