You prompt an AI coding assistant to build a game, and it does — sort of. The first prototype runs, but the code is one long file, the magic numbers are hardcoded, nobody checked whether the jump feels right, and there is no design document to explain why the game works the way it does. That is the problem this guide solves: how to build a game with Claude Code Game Studios, by giving one Claude Code session the structure of a small studio instead of leaving it as one general-purpose chat.

The core idea is simple. A solo developer working with AI has no structure: nobody stops a bad shortcut, nobody asks whether a feature fits the game's vision, and there is no quality pass before the game ships. Claude Code Game Studios answers that by organizing the session into a studio hierarchy — directors who guard the vision, department leads who own their domains, and specialists who do the hands-on work — with slash-command skills for every phase from brainstorming to release.

What Claude Code Game Studios is

Claude Code Game Studios is an open-source project template for Claude Code, not a plugin and not a finished game. You clone it, and the clone becomes your game's project folder: the files under .claude/ supply the agents, skills, hooks, and rules, and you start Claude Code in that folder. According to its README, checked on 2026-11-03, it contains 49 agents, 74 skills, 15 hooks, 14 rules, and 62 document templates. One discrepancy to know about: the repository's own short description still says 72 workflow skills, while the README says 74. This guide uses the README's 74, since the README also lists the commands, and the difference is worth flagging rather than hiding.

The 49 agents sit in three tiers. Tier 1 is three directors: creative-director, technical-director, and producer. Tier 2 is eight department leads, including game-designer, lead-programmer, art-director, audio-director, narrative-director, qa-lead, release-manager, and localization-lead. Tier 3 is the specialists, from gameplay-programmer and level-designer to qa-tester and accessibility-specialist. There are also engine-specific agent sets for Godot 4, Unity, and Unreal Engine 5.

It is built for Claude Code only, as far as its README states. Community discussion about ports to other tools exists, but no other platform is claimed in the README, so this guide does not promise Codex or Cursor support. The repository is MIT licensed, and on the repository page checked on 2026-11-03 it showed 33,692 stars and 4,528 forks. Created on 2026-02-12, it is an older template whose attention surged in late October — a healthier signal than a one-day spike.

Install and use

The commands below are quoted verbatim from the project's README. They were not executed in this run, so a successful install on your machine is unverified until you run them yourself.

First, check the prerequisites from the README: Git; Claude Code, where the native installer is recommended and npm install -g @anthropic-ai/claude-code also works on Node.js 22+; Python 3, which reads project.yaml for every skill and hook; and Bash, which runs every hook. The README also recommends jq for hook validation.

Then clone the template as your game project:

git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-game
cd my-game

Open Claude Code in the project's root folder — the one holding CLAUDE.md and project.yaml — and start a session:

claude

Starting in a subfolder such as src/ is a real trap the README warns about: it skips the project's hooks, deny rules, and ask-first permission mode. Always start at the root.

Then run /start. The system asks where you are — no idea, vague concept, clear design, or existing work — and guides you to the right workflow. Or jump straight to a skill you already know you need:

/brainstorm
/setup-engine godot 4.7
/project-stage-detect

/brainstorm explores game ideas from scratch, /setup-engine godot 4.7 configures your engine, and /project-stage-detect analyzes an existing project. From there: design with /map-systems and /design-system, plan with /create-epics and /create-stories, build with /dev-story, close with /story-done, and review with /design-review, /code-review, and /balance-check. For release: /release-checklist, /launch-checklist, /changelog, /patch-notes, and /hotfix.

One setting matters more than the rest: modes.rigor in project.yaml, with three levels — minimal, standard, and full. The README is unusually honest about the trade-off. In its own measurement, four games were built from one brief at different rigor levels, and the documents each wrote before its first line of game code were counted: minimal wrote 1 (the one-page brief), while standard wrote 30 and took 58 minutes. All produced a running, tested game, but two blind reviewers and a human playtest ranked the standard build last — the extra 29 documents bought traceability, not a better game. That is why minimal is the default. Raise the rigor with /settings only when the project grows, for example /settings modes.rigor=full.

There is also a quality rule worth building your habits around. A story that changes anything the player sees is not closed until the game has been launched, observed, and a screenshot retained in production/qa/evidence/. A passing test says nothing about a menu drawn off-screen. At every rigor level, including minimal, the look is not waived.

Where it fits, and where it does not

This template fits best when you are a solo developer or a tiny team building an original game and you want the AI's work to be checkable: a Godot, Unity, or Unreal project where design decisions, code reviews, QA evidence, and release checklists should survive longer than one chat session. It fits game jams too, provided you stay on minimal rigor.

It does not fit every project. If you only need one small script or a single mechanic prototype, 49 agents and 74 skills are more process than the job needs; a plain Claude Code session will get you there faster. It is not a game engine, it does not include a finished game to reskin, and it does not replace the licenses or costs of the engine, Claude Code, or any external assets. And it is not a shortcut for copying someone else's game: build an original game with it, and keep your own art, music, and code clean.

A few cautions are worth keeping. First, cost: the README says the three directors ask for Opus, lead-programmer and fifteen specialists name Sonnet, and the remaining thirty inherit your session's model — so the director reviews are the expensive part. Second, hooks fail gracefully if optional tools are missing, with one exception: a commit that stages data JSON is blocked when there is no Python to validate it, so install Python 3 before you rely on the hooks. Third, the skill count discrepancy (72 in the repository description, 74 in the README) is a reminder to check the README on the day you install.

FAQ

What is Claude Code Game Studios? It is an open-source, MIT-licensed project template that turns a single Claude Code session into a small game studio: 49 specialist agents in three tiers, 74 slash-command skills, 15 hooks, 14 rules, and 62 document templates, according to its README. You clone it as your game project; it is not a plugin and it does not ship a finished game.

How do I install Claude Code Game Studios? Clone it as your project folder with git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-game, open Claude Code in the project root with claude, and run /start. You need Git, Claude Code on Node.js 22+, Python 3, and Bash first; jq is recommended. These commands are quoted from the README and were not executed in this run.

Which game engines does Claude Code Game Studios support? Three, with a dedicated specialist agent set for each: Godot 4, Unity, and Unreal Engine 5. Configure yours with /setup-engine, for example /setup-engine godot 4.7.

Should I use minimal, standard, or full rigor? Start with minimal, the default. The README's own measurement found that standard wrote 30 documents before its first line of code and took 58 minutes, yet blind reviewers and a human playtest ranked that build last — the extra documents bought traceability, not a better game. Raise rigor with /settings when the project grows.

Does Claude Code Game Studios write the game for me? No. You still make every decision; the template gives you a team that asks the right questions, catches mistakes early, and keeps the project organized from first brainstorm to launch. A story that changes what the player sees is not closed until the game has been launched, observed, and screenshotted as QA evidence.

Can I use Claude Code Game Studios for a game jam? Yes, and minimal rigor is designed for exactly that: jam-game speed, a one-page brief, terse docs, minimal QA evidence, and solo review. The typical jam path is /start, then /setup-engine, /brainstorm, /create-stories, and /dev-story paired with /story-done.

See the skill's directory entry for install, platforms, and quick start: Claude Code Game Studios on aiskills.one.