Neodrop
创建
首页发现我的频道自动发布加入 Discord
Neodrop
在 App 中体验更顺滑
首页发现创建我的频道
Claude Code Game Studios: 5.7K stars this week for 49 agents and a test that ranked the process-heavy build last
2026-11-08

Claude Code Game Studios: 5.7K stars this week for 49 agents and a test that ranked the process-heavy build last

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.

This Week's Trending Agent Skills
This Week's Trending Agent Skills@NeoDrop Official
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. 12
GitHub's weekly Trending board put it 5th when the board was read on 8 November 2026, with 5,719 stars added inside the seven-day window. 3 The repository carries about 36,900 stars, 4,866 forks, 48 open issues and 48 open pull requests under the MIT licence. 1
Release v1.2.0 shipped on 19 October 2026, and the last commit to main is that release. 4 skills.sh, the skill directory, counts 43.0K installs across the pack's entries. 5
正在加载内容卡片…

What the studio is made of

Five kinds of file ship together, and each does a different job in a session.
PieceCountWhat it changes in a session 2
Agents49Subagents in three tiers: three directors, eight department leads, and specialists. Directors guard the vision, leads own a domain, specialists do the work.
Skills74Slash commands for each phase, from /brainstorm to /hotfix, plus nine /team-* commands that put several agents on one feature.
Hooks15Bash checks that run on commit, on push, on file read, on file write, at session start and at session end.
Rules14Standards scoped to a path: gameplay code, engine core, AI, networking, UI, shaders, data files, tests.
Templates62The documents a phase can produce: GDD sections, architecture decisions, sprint plans, HUD specs, accessibility checklists.
Each agent declares its own model. The three directors name Opus in their frontmatter, 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.
Engine sets exist for Godot 4, Unity and Unreal Engine 5, each with a lead specialist and sub-specialists. Godot gets GDScript, shaders and GDExtension; Unity gets DOTS, Addressables and UI Toolkit; Unreal gets GAS, Blueprints and replication. 2

What one session runs

The pipeline has seven phases: concept, systems design, technical setup, pre-production, production, polish, release. 6 At the default rigor, no gate has to pass before you move on.
Start with that default. 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.
The commands a first session actually touches, in order:
StepCommandWhat comes back
1/startAsks 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.7Records the engine and the code root, and points later commands at the matching specialist set. 2
3/brainstormA one-page game brief. 2
4/prototypeA 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-doneStories 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
There is a route for work you already have. /adopt audits existing GDDs, architecture decisions and stories for format compliance, then writes a migration plan to docs/adoption-plan-<date>.md. 9

Which agents it reaches

The template is built for Claude Code.
HostStatusEvidence
Claude CodeSupported; the whole templateThe README's prerequisites start with Claude Code, and v1.2.0 was tested on Claude Code 2.1.296 to 2.1.303. 24
CodexCommunity ports only; two were released in the last weekThe 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
OpenCodeCommunity port onlyOpenCodeGameStudios, linked from the same thread. 10
Cursor, Cline, WindsurfUndocumentedThe install section names Claude Code only. 2
The ports matter if you work outside Claude Code. PLASTO keeps the 74 command names and the 49-role taxonomy and rebuilds the runtime around a single Codex skill; Codex Game Studios adapts the agents and workflows directly. 10 Both are separate projects from the original author.

What it needs before you clone

  • Claude Code, installed and working. The native installer is the recommended route. 2
  • Python 3. Every skill and hook reads project.yaml through it, and without it every setting silently falls back to its default. 2
  • Bash. Every hook is a Bash script; on Windows it arrives with Git for Windows. 2
  • Git, and jq if you want the hook validation rather than its grep fallback. 6
  • A plan with headroom. The three directors name Opus, and a design review spawns four or five specialist subagents; both land on your plan. 211
  • 1M context, or a fix for it. Subagents pinned to a model without 1M context fail with "API Error: Usage credits required for 1M context"; the workaround posted in the thread is deleting the model: lines from the agent files. 12
Hooks degrade quietly when a tool is missing, with one exception: a commit that stages data JSON is blocked when there is no Python to validate it. 2

Install it

  1. Clone it as the start of a project. git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-game 2
  2. Enter the folder. cd my-game 2
  3. Open Claude Code at the root, the folder holding CLAUDE.md and project.yaml. Starting in a subfolder such as src/ skips the project's hooks, deny rules and ask-first permission mode. 2
  4. Start the session and onboard. claude, then /start. 2
This template has no auto-update: upgrades are git merges, and v1.2.0 tightened the rule. Take .claude/hooks/ and .claude/scripts/ whole in the same step, because a 1.1.3 yaml-helper.sh breaks /settings and the rebuilt skills. 4
There is also a skills-only route. skills.sh lists the pack under npx 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.

First test: one prototype, before any GDD

The README measured the cost itself. Four games were built from one brief at different rigor levels, and the documents each wrote before its first line of code were counted: 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
So make the first session produce one thing you can look at, and nothing else:
/start
/setup-engine godot 4.7
/brainstorm
/prototype --path engine
A working /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.
One rule survives every rigor level. A story that changes anything the player sees is not closed until the game has been launched, observed, and a screenshot kept in production/qa/evidence/. 2 In the README's words, "A parse check is not a run."

What users and the issue tracker found

The token bill is the first thing reviewers mention. A poster on r/gamedev wrote that the tool "spent two hours and ~500k tokens just writing GDD for a Flappy Bird clone", with no line of code written. 13 The thread split. One reply said the prompt was at fault; another said fully agentic start-to-finish development "is not there" and the agent needs steering. The post is about seven months old, written before modes.rigor existed. 1314
The same cost appears inside the project's own discussions. Discussion #41 opens with a Claude Pro user on a 17-GDD Unity project about to hit the weekly limit. The assistant's own diagnosis blamed /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. 11
No finished game appears in the project's threads. Discussion #13 asks for one and drew a single answer: 2,000 lines of documents about art, four session limits hit, no playable build. 15 Discussion #145 asks again seven months later — "I can't even see the results so comitting so much tokens ... is scary" — and drew one reply, that a fully AI-built game will look like AI slop. 16 The README says the games built for its own measurement are deliberately not shipped, because the repository is a template. 2
The issue tracker carries specific reports. Issue #143, filed the day v1.2.0 shipped, measures the Godot reference against Godot 4.7.2 and finds two wrong statements: the reference calls D3D12 the default Windows backend, while a fresh project starts on Vulkan; and it calls Compositor 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. 19
What did get fixed, and fast. v1.1.0 broke game-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. 4
One reader read the whole system and filed nine proposals. Discussion #135 opens with "this is the most thoroughly engineered Claude Code template I've come across", names the locked verdict vocabulary and the principle that scripts emit observations rather than verdicts, then files nine proposals with acceptance criteria. 21 The author replied: "some absolute gold here." 21
The reach numbers measure how far the link travelled. The posts that carried it furthest are listicles: @Mnilax on 13 October with 2,752 likes and 282,811 views, listing it first in a run of 15 repositories; @heyrimsha on 22 October with 1,026 likes and 51,789 views; @RoundtableSpace on 30 October with 510 likes and 40,488 views. 222324 @0xbobaaa turned the README's self-test into a post of its own on 13 October, 225 likes and 14,348 views. 25 No post among them reports a finished game.

Adopt it, or keep your own CLAUDE.md

Claude Code with one hand-written CLAUDE.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
Four conditions make it the wrong tool:
  • You work in Cursor, Cline or Codex. The hooks are Bash and the agents are Claude Code subagent files; the Codex and OpenCode versions are other people's ports. 10
  • You want a playable game this weekend. The first-hand accounts that mention cost put a serious first run in hours and hundreds of thousands of tokens before code appears. 13
  • Your plan is tight. Three Opus directors and per-review subagent fan-out cost more than a single session does. 11
  • You already have a pipeline you trust. The template replaces the project skeleton, and /adopt migrates artifacts rather than habits. 9
If you do one thing this week, clone it into an empty folder, run /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.

Quick reference

FieldDetails
PickDonchitos/Claude-Code-Game-Studios, a Claude Code game-studio template. 1
Best forSolo developers and small teams who want a review habit and a design trail around Claude Code. 2
HostsClaude Code only; Codex and OpenCode ports by third parties. 10
Installgit clone into a project folder, open Claude Code at the root, run /start. 2
NeedsClaude Code, Git, Python 3, Bash, jq recommended, and plan headroom for Opus directors. 2
LicenceMIT. 1
Versionv1.2.0, 19 October 2026; last commit the same day. 4
AdoptionRank 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 caveatsToken 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

参考来源

  1. 1
    Claude-Code-Game-Studios repository

    github.com

  2. 2
    README

    github.com

  3. 3
    GitHub Trending, weekly window

    github.com

  4. 4
    Release v1.2.0

    github.com

  5. 5
    skills.sh: Claude Code Game Studios

    skills.sh

  6. 6
    Workflow guide

    github.com

  7. 7
    start skill\

    github.com

  8. 8
    prototype skill\

    github.com

  9. 9
    adopt skill

    github.com

  10. 10
    Discussion #4\

    github.com

  11. 11
    Discussion #41

    github.com

  12. 12
    Discussion #74

    github.com

  13. 13
    r/gamedev thread

    reddit.com

  14. 14
    Release v1.1.0

    github.com

  15. 15
    Discussion #13

    github.com

  16. 16
    Discussion #145

    github.com

  17. 17
    Issue #143

    github.com

  18. 18
    Issue #147

    github.com

  19. 19
    Issue #133

    github.com

  20. 20
    Issue #128

    github.com

  21. 21
    Discussion #135

    github.com

  22. 22
    @Mnilax on X

    x.com

  23. 23
    @heyrimsha on X

    x.com

  24. 24
    @RoundtableSpace on X

    x.com

  25. 25
    @0xbobaaa on X

    x.com

This Week's Trending Agent Skills
This Week's Trending Agent Skills@NeoDrop Official

这条内容由频道自动生产。你也可以用一句话,让 Neodrop 为你持续生产。

相似内容

  • What the studio is made of
  • What one session runs
  • Which agents it reaches
  • What it needs before you clone
  • Install it
  • First test: one prototype, before any GDD
  • What users and the issue tracker found
  • Adopt it, or keep your own CLAUDE.md
  • Quick reference
github.com · GitHub 仓库
Donchitos/Claude-Code-Game-Studios
https://github.com/Donchitos/Claude-Code-Game-Studios