Claude Code Game Studios workflow
A Claude Code project template for game development: a studio hierarchy of agents, skills for every phase, hooks, rules and doc templates
- 29,167 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Hooks run shell scripts on commits and at session start
- Agents write project files and documentation
Install
- Works in
Manual install
git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-gameOpen the my-game folder in Claude Code and run /start.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks run shell scripts on commits and at session start
- Agents write project files and documentation
This is third-party code. Review the repository files before installing.
What it does
The template turns a Claude Code session into a game studio with three tiers of agents: directors guard the vision, department leads own their areas and specialists do hands-on work. Slash commands cover the whole cycle: concept and game design, art bible, architecture decisions, epics and stories, sprints, reviews, QA, release and patches. Hooks validate commits, asset changes and documentation gaps, and path-scoped rules set standards for gameplay, network and UI code. Agent sets are included for Godot 4, Unity and Unreal Engine 5.
Who it is for. For indie game developers and small teams running a project with Claude Code.
Good fit when
- You are starting a game and want structure from concept to release
- You need design docs, ADRs and sprints in one format
- You want the agent to check decisions against the game's vision
Not a fit when
- The project is not a game
- You want light coding help without studio processes
Example request
/start I have an idea for a co-op roguelike about a bakery, help me shape the conceptLimitations
Built for Claude Code, with agents using Opus, Sonnet and Haiku, so subscription usage is noticeable. It installs as the base of a new project via clone; adopting it in an existing project through /adopt requires migrating documents. It is process-heavy, so switch review mode to lean or solo for small prototypes.
How to disable. Remove the template's .claude folder with its agents, skills, hooks and rules from the project.
FAQ
Which engines are supported?
Godot 4, Unity and Unreal Engine 5, each with its own lead agent and sub-specialists.
Can I reduce the number of approval gates?
Yes, review mode full, lean or solo is set during /start or in production/review-mode.txt.
Discussion
No questions or reviews yet.
Related
WorkflowsA set of Claude Code utilities: background skills, expert agents, slash commands and prompt templates for development
A ready-made Claude Code setup: agents, slash commands, skills, safety hooks, rules and MCP connections in one install
A starter kit for Claude Code: a CLAUDE.md memory-bank template with ready hooks, subagents and skills you copy into your project
A universal workflow plugin for Claude Code: 7 agents, 26 commands, 14 skills and 14 hooks for any project
A Claude Code template: wireframe, prototype and an HTML spec before the code, then a build with the native plan and goal modes
A ready harness for Claude Code and Codex: spec-driven development, TDD, memory between sessions, quality gates and human checkpoints
README in short
The README explains why a solo developer benefits from studio structure and lists the contents: agents, skills, hooks, rules and doc templates. It shows the agent hierarchy, a table of engine specialists and the full command list by phase. Getting started means cloning into your game folder, opening it in Claude Code and running /start. It also covers upgrading, project structure, customization and platforms. MIT licensed.