Oleksandr Kuzmenko, EditorPublished 6 min readAI-assisted · editor-reviewed
TL;DR
- Enforces 49 specialized agent roles across production, programming, design, and audio.
- Includes 74 slash commands for system design, epic creation, sprint planning, and QA checks.
- Requires screenshot evidence in production/qa/evidence/ before UI stories can be closed.
Key facts
- Total Specialized Agents
- 49
- Custom Slash Skills
- 74
- Supported Game Engines
- Godot 4.7+, Unity, Unreal Engine
- Rigor Configuration Modes
- minimal, standard, full
Source: Key facts — Total Specialized Agents, Custom Slash Skills
Source: Key facts. Total Specialized Agents: 49. Custom Slash Skills: 74. The chart compares only values that share a unit. Each figure is copied from the story.
Metric chart
- 49Total Specialized Agents
- 74Custom Slash Skills
- Total Specialized Agents49
- Custom Slash Skills74
Studio Hierarchy and Model Allocation
Claude Code Game Studios structures a solo prompt into a 49-agent hierarchy split across three operational tiers. High-level planning relies on three directors (creative-director, technical-director, producer) requesting Opus frontmatter. Domain management (lead-programmer, art-director, and fifteen specialists) defaults to Sonnet, while thirty execution-level specialists inherit the active session model to control token burn.
Engine-specific agent profiles ship natively for Godot (4.7+), Unity (DOTS/ECS, UI Toolkit, Addressables), and Unreal Engine (GAS, Blueprints, UMG).
Slash Commands and Quality Gates
The repository introduces 74 workflow skills invoked directly via slash commands:
- Lifecycle & Architecture:
/start,/setup-engine,/map-systems,/create-architecture,/architecture-decision. - Task Tracking:
/create-epics,/create-stories,/dev-story,/story-done. - Verification:
/gate-check,/smoke-check,/regression-suite,/perf-profile.
A strict visual QA gate blocks task completion for any visual or UI code changes until the game is launched and a screenshot is saved under production/qa/evidence/.
Setup and Governance
The framework uses Bash hooks and Python 3 to parse project.yaml. The modes.rigor parameter controls execution depth:
minimal(default): jam speed, solo reviews, concise docs, basic QA.standard: 5 mandatory GDD sections, balanced documentation, lean review.full: 8 GDD sections, comprehensive testing evidence, full director reviews.
Try it in 2 minutes
git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-game
cd my-game
claude
/startWhen to use
- Building indie games solo with Claude Code where feature drift and messy commits are common risks.
- Prototyping in Godot, Unity, or Unreal Engine while requiring clear architectural documentation.
- Working on gameplay features that need multi-agent coordination across design, code, and QA.
What to do today
- Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a new project directory.
- Run claude in the repository root and execute /start to initialize project.yaml.
- Set modes.rigor to minimal for rapid prototyping or standard for long-term architectures.
Step names are taken from What to do today.
Step names are taken from What to do today. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a new project directory.. Run claude in the repository root and execute /start to initialize project.yaml.. Set modes.rigor to minimal for rapid prototyping or standard for long-term architectures.
- Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a new project directory.
- Run claude in the repository root and execute /start to initialize project.yaml.
- Set modes.rigor to minimal for rapid prototyping or standard for long-term architectures.