
This week's pick is Donchitos/Claude-Code-Game-Studios, a Claude Code template that turns one session into a 49-agent game studio: the clone-and-onboard steps, a one-prototype first test that costs one session instead of thirty documents, and what users' token bills and the open bugs say about it.
Claude-Code-Game-Studios is a game project template you clone. Open the folder at its root in Claude Code and one session inherits 49 subagents, 74 slash commands, 15 hooks and 14 path-scoped rules. 12main is that release. 4 skills.sh, the skill directory, counts 43.0K installs across the pack's entries. 5| Piece | Count | What it changes in a session 2 |
|---|---|---|
| Agents | 49 | Subagents in three tiers: three directors, eight department leads, and specialists. Directors guard the vision, leads own a domain, specialists do the work. |
| Skills | 74 | Slash commands for each phase, from /brainstorm to /hotfix, plus nine /team-* commands that put several agents on one feature. |
| Hooks | 15 | Bash checks that run on commit, on push, on file read, on file write, at session start and at session end. |
| Rules | 14 | Standards scoped to a path: gameplay code, engine core, AI, networking, UI, shaders, data files, tests. |
| Templates | 62 | The documents a phase can produce: GDD sections, architecture decisions, sprint plans, HUD specs, accessibility checklists. |
lead-programmer and fifteen specialists name Sonnet, and the other thirty inherit whatever model your session runs. 2 The README describes the tiers as seniority of role.modes.rigor takes minimal, standard or full, and stands in front of six knobs: workflow, document density, QA level, story granularity, review mode and team size. 2 /start asks for it once.| Step | Command | What comes back |
|---|---|---|
| 1 | /start | Asks where you are — no idea, vague idea, clear concept, existing work — then writes project.stage, modes.rigor and modes.automation to project.yaml after you confirm. 7 |
| 2 | /setup-engine godot 4.7 | Records the engine and the code root, and points later commands at the matching specialist set. 2 |
| 3 | /brainstorm | A one-page game brief. 2 |
| 4 | /prototype | A throwaway HTML, engine or paper build, closed with one of four verdicts: PROCEED, PIVOT, KILL or NOT ASSESSED. 8 |
| 5 | /create-stories → /dev-story → /story-done | Stories with acceptance criteria, the implementation, then the closing check. 2 |
/start assumes no engine, no idea and no experience, and it deliberately never runs the next step for you. 7 /prototype is a gate of its own, separate from /vertical-slice: it runs after /brainstorm and before any design document exists. 8/adopt audits existing GDDs, architecture decisions and stories for format compliance, then writes a migration plan to docs/adoption-plan-<date>.md. 9| Host | Status | Evidence |
|---|---|---|
| Claude Code | Supported; the whole template | The README's prerequisites start with Claude Code, and v1.2.0 was tested on Claude Code 2.1.296 to 2.1.303. 24 |
| Codex | Community ports only; two were released in the last week | The author answered a Codex request in March by saying he would like the project platform-agnostic one day. 10 PLASTO Game Studio shipped v1.0 on 3 November and Codex Game Studios was announced on 6 November, both in that thread. 10 |
| OpenCode | Community port only | OpenCodeGameStudios, linked from the same thread. 10 |
| Cursor, Cline, Windsurf | Undocumented | The install section names Claude Code only. 2 |
project.yaml through it, and without it every setting silently falls back to its default. 2jq if you want the hook validation rather than its grep fallback. 6model: lines from the agent files. 12git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-game 2cd my-game 2CLAUDE.md and project.yaml. Starting in a subfolder such as src/ skips the project's hooks, deny rules and ask-first permission mode. 2claude, then /start. 2.claude/hooks/ and .claude/scripts/ whole in the same step, because a 1.1.3 yaml-helper.sh breaks /settings and the rebuilt skills. 4npx skills add donchitos/claude-code-game-studios, which puts the skill files into an agent's skills directory. 5 That route installs the skill files alone; the 49 agent definitions, the hooks and the rules live outside .claude/skills/. It suits lifting one command into a project that already has its own structure.minimal wrote 1, the one-page brief; standard wrote 30 and took 58 minutes. 2 All of them produced a running, tested game. Two blind reviewers and a human playtest then ranked the standard build last. 2/start
/setup-engine godot 4.7
/brainstorm
/prototype --path engine/prototype run ends in one of four verdicts, and the build it leaves is throwaway by design. 8 If the prototype is something you would keep playing, raise the process weight with /settings modes.rigor=standard and start the document path. If it is not, you have spent one session instead of thirty documents.production/qa/evidence/. 2 In the README's words, "A parse check is not a run."modes.rigor existed. 1314/design-review, which spawns four or five specialist subagents per run, across 14 runs on two documents. 11 In the replies, one user described routing Claude Code through a cheaper model to contain the bill. 11Compositor a node, while in 4.7.2 it is a Resource assigned to a WorldEnvironment. 17 It is open with no reply. Issue #147 shows set-stage.sh rewriting project.yaml before production/stage.txt, with no rollback if the second write fails. 18 Issue #133 shows the commit hook checking eight GDD headings that disagree with the template and /design-system; the subfolder false positives were fixed in 1.2.0, and the heading list waits for 2.0.0. 19game-designer and creative-director: a preloaded skill's config command was denied by the agent's own disallowedTools: Bash, so the subagent never started. 20 v1.1.1 shipped the day after the report. v1.2.0 also removed a bare Bash grant from 34 skills, which now pre-approve only the commands they run. 4CLAUDE.md already gets you conventions, and an engine MCP server gets the agent into the editor. This template adds two things that setup lacks: gates that stop a story closing without evidence, and path-scoped rules that change with the folder you touch. 2/adopt migrates artifacts rather than habits. 9/start as someone with no idea, and let /prototype build one throwaway thing. One session tells you whether these are the questions you want asked of your game.| Field | Details |
|---|---|
| Pick | Donchitos/Claude-Code-Game-Studios, a Claude Code game-studio template. 1 |
| Best for | Solo developers and small teams who want a review habit and a design trail around Claude Code. 2 |
| Hosts | Claude Code only; Codex and OpenCode ports by third parties. 10 |
| Install | git clone into a project folder, open Claude Code at the root, run /start. 2 |
| Needs | Claude Code, Git, Python 3, Bash, jq recommended, and plan headroom for Opus directors. 2 |
| Licence | MIT. 1 |
| Version | v1.2.0, 19 October 2026; last commit the same day. 4 |
| Adoption | Rank 5 on the weekly board with 5,719 stars in the window; about 36,900 stars; 43.0K directory installs. 35 |
| First test | /start → /setup-engine → /brainstorm → /prototype, then decide. 8 |
| Main caveats | Token burn reported in hours and hundreds of thousands of tokens; no published finished game; Godot reference errors open in #143; last commit 19 October. 1317 |
github.com
github.com
github.com
github.com
skills.sh
github.com
github.com
github.com
github.com
github.com
github.com
github.com
reddit.com
github.com
github.com
github.com
github.com
github.com
github.com
github.com
github.com
x.com
x.com
x.com
这条内容由频道自动生产。你也可以用一句话,让 Neodrop 为你持续生产。