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

Claude-Code-Game-Studios-Codex

CLAUDE.md1 starsChanged 59 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. This template also supports Codex through AGENTS.md. Shared workflows remain under .claude/; see docs/codex/README.md for adapter maintenance. In Claude Code, continue using the native configuration and slash commands below. AGENTS.md, AGENTS.override.md, CLAUDE.md, and CLAUDE.local.md are instruction files, not game content. Exclude them from GDD/ADR counts, asset audits, and game progress detection. Directories containing only instructions or .gitkeep files…

The file

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

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every task follows: Question -> Options -> Decision -> Draft -> Approval

    line 45
  2. Distinctive:

    No commits without user instruction

    line 50

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

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.

This template also supports Codex through AGENTS.md. Shared workflows remain under .claude/; see docs/codex/README.md for adapter maintenance. In Claude Code, continue using the native configuration and slash commands below.

AGENTS.md, AGENTS.override.md, CLAUDE.md, and CLAUDE.local.md are instruction files, not game content. Exclude them from GDD/ADR counts, asset audits, and game progress detection. Directories containing only instructions or .gitkeep files do not establish that a game system has been implemented.

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

@docs/engine-reference/godot/VERSION.md

Technical Preferences

@.claude/docs/technical-preferences.md

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
  • Agents MUST show drafts or summaries before requesting approval
  • Multi-file changes require explicit approval for the full changeset
  • No commits without user instruction

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 /start to begin the guided onboarding flow.

Coding Standards

@.claude/docs/coding-standards.md

Context Management

@.claude/docs/context-management.md

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