49 AI agents walk into a game studio — you still make the coffee
A Claude Code template that turns one chat session into a structured game dev team with hierarchy, slash commands, and enough process to maybe stop you from hardcoding magic numbers.

What it does
This is a configuration template for Claude Code that simulates a full game development studio inside a single chat session. It defines 49 specialized agents — from creative director down to QA tester — plus 73 slash-command skills, 12 bash hooks, and 41 document templates. You clone the repo, open Claude Code, type /start, and the system routes you through brainstorming, design, sprints, code review, and release checklists based on your project’s actual stage.
The interesting bit
The hierarchy isn’t decorative. Agents have delegated authority boundaries, escalation paths for cross-domain conflicts, and a strict “ask first, draft second, you approve last” protocol. The hooks are the quiet workhorse: they validate commits for hardcoded values, catch missing design docs when code exists, and archive session state before Claude’s context window compacts. It’s process-as-code for a single developer who knows they’ll skip the boring parts without a nagging producer.
Key highlights
- 49 agents in three tiers (directors, department leads, specialists) with engine-specific subsets for Godot 4, Unity, and Unreal Engine 5
- 73 slash commands covering full lifecycle:
/brainstorm,/create-epics,/dev-story,/story-done,/perf-profile,/release-checklist,/team-combat - 12 bash hooks for automated validation on commits, asset changes, session lifecycle, and gap detection
- 11 path-scoped coding rules enforced when editing gameplay, engine, AI, UI, or network code
- Explicitly not autonomous: agents present 2-4 options, you decide, nothing writes without sign-off
Caveats
- Requires Claude Code (Anthropic’s CLI tool) and works within its session model; this is prompt engineering and shell scripts, not a standalone engine
- Hooks recommend
jqand Python 3 but degrade gracefully without them — validation just skips - README notes some hooks fire on every tool call and exit early when irrelevant, which suggests the implementation leans on Claude Code’s hook granularity rather than native git hooks
Verdict
Solo indie devs using Claude Code who keep shipping spaghetti because nobody reviews their design docs. Not useful if you already have a team, a producer, or you hate being asked to write architecture decision records before coding.