Claude Code Game Studios is a setup that organizes Claude Code into a coordinated game-development team of specialized AI agents. It supports game projects across design, programming, art, audio, narrative, quality assurance, and production, with skills and workflows for coordinating that work.
Borrowing it
Nothing to install: this file belongs to Donchitos/Claude-Code-Game-Studios. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Donchitos/Claude-Code-Game-Studios/main/CLAUDE.mdgit clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-StudiosWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/donchitos/claude-code-game-studios/claude-md)<a href="https://agentmods.dev/instructions/donchitos/claude-code-game-studios/claude-md"><img src="https://agentmods.dev/badge/instructions/donchitos/claude-code-game-studios/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/donchitos/claude-code-game-studios/claude-md"><img src="https://agentmods.dev/badge/instructions/donchitos/claude-code-game-studios/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00826 | $0.00826 |
| Opus 5.5 | $0.00330 | $0.00330 |
| Sonnet 5.5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
Claude-Code-Game-Studios CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- Claude-Code-Game-Studios CLAUDE.md — 92% identical, 35 lines differ
- youtube-example-ai-studio CLAUDE.md — 88% identical, 45 lines differ
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
@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 not 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
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago Changed · -1 tokens per session d8dda907c8a1
- 18d ago Changed · +6 lines · +99 tokens per session d6bb1efc8824
- 1mo ago Changed · +23 lines · +347 tokens per session af8cdfee1b99
- 1mo ago First seen · 55 lines · 381 tokens per session scan A a734e23d0c54
Claude-Code-Game-Studios CLAUDE.md is an instructions file published in the GitHub repository Donchitos/Claude-Code-Game-Studios (27,690 stars, last pushed 8d ago), licensed MIT. It adds 826 tokens to every session, about $0.0033 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.