A project template that turns a Claude Code session into a game studio: 49 clearly defined agents (three tiers: directors, department heads, and specialists), 74 slash command skills, 15 hooks, and 14 path-specific coding standards, covering everything from ideation to release.
Star count 29212 (+353 / 24h)
Rationale
- Includes specialist agents for three engines: Godot 4, Unity, and Unreal 5; the three director roles require Opus, lead-programmer and 15 specialists are assigned Sonnet, while the remaining 30 agents follow the model used in your session
- modes.rigor offers three levels: minimal, standard, and full, with minimal as the default; the author compared these using the same brief, finding that standard mode produced 30 documents and took 58 minutes before writing the first line of game code, yet ranked last in blind reviews and human playtests
- Any change affecting player-visible content must be verified by actually launching the game, observing it, and saving screenshots to production/qa/evidence/ before the task can be closed
Usage
- Run git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-game, start claude in the root directory containing CLAUDE.md and project.yaml, and enter /start
- Alternatively, use /brainstorm, /setup-engine godot 4.7, or /project-stage-detect directly; adjust workflow intensity with /settings modes.rigor=full
- Requires Git, Claude Code, Python 3, and Bash (on Windows, use the version included with Git for Windows); installing jq is recommended
Risks
- With many agents and skills, and director-level roles using Opus, token costs can be high; the author's own comparison shows that heavier workflows do not necessarily produce better games
- Claude Code must be launched from the project root directory, otherwise hooks, prohibition rules, and the ask-before-acting permission mode will not take effect; the repository was created in 2026 2, licensed under MIT