Claude-Code-Game-Studios
Turn Claude Code into a full game dev studio, 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Runs with mockssource: GitHubShellMITcommit 7ed2c3e9c46c
Shell, MIT licensed. The project labels itself: ai agents, ai assisted development, anthropic, claude, claude code, game design, game development and gamedev.
Claude-Code-Game-Studios runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 14 hooks pass syntax and runtime checks, all 8 scripts pass syntax and runtime checks, all 74 skills have valid frontmatter and sections, all 49 agents exist in catalog, all 148 spec files exist at declared paths, the config resolution pipeline works correctly, and Claude Code CLI v2.1.282 is available but requires interactive login.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Claude Code CLI requires interactive login (no CLAUDE_API_KEY / ANTHROPIC_API_KEY set)1 minute
- PyYAML not installed for Python 30.5 minutes
- Node.js 18.19.1 below Claude Code requirement >=22.0.0
- Install time
- 7 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- bash -n on all 22 .sh files (all clean); executed session-start.sh (branch HEAD, review mode solo, 180ms), all 13 other hooks (all exit 0), all 8 scripts (all exit 0); yaml-helper.sh resolve_config returns correct full config; Python catalog validation: 74 skills + 49 agents all match disk with 0 missing spec files
- Model tokens used
- 253,963
- Exact commit tested
- 7ed2c3e9c46c
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **All 74 skills** exist on disk, in `catalog.yaml`, each has a valid `SKILL.md` with correct fron… - **All 49 agent files** exist on disk and in catalog - **All spec files** (74 skill specs + 49 agent specs) exist at their catalog-declared paths - **All 14 hook scripts** (`session-start.sh`, `detect-gaps.sh`, `validate-commit.sh`, `validate-pu… - **All 8 scripts** — same syntax and runtime verification - **`yaml-helper.sh resolve_config`** works correctly, resolving all config keys including rigor/au… - **`session-start.sh`** runs in 180ms, outputs branch info and review mode **Errors encountered:** 1. **PyYAML not installed** — `python3 -c "import yaml"` failed on initial attempt. Fixed by `pip3 … 2. **Claude Code CLI not authenticated** — The CLI binary (v2.1.282) is available via `npx` but req… 3. **Node.js version mismatch** — Claude Code requires Node >=22.0.0; container has Node 18.19.1. T… **No mock stood up** — this framework has no external service dependencies that require mocks. It's…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 6.5 minutes to install, slower than the median of the 18 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 19 ai-agents projects Argusic has installed and timed, Claude-Code-Game-Studios was the 11th fastest to reach a running state, and 12 of 19 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
ai-agentsai-assisted-developmentanthropicclaudeclaude-codegame-designgame-developmentgamedevgodotindie-game-devunityunreal-engine
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/claude-code-game-studios)Questions
- Does Claude-Code-Game-Studios run?
- Claude-Code-Game-Studios runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test Claude-Code-Game-Studios?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7ed2c3e9c46c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Claude-Code-Game-Studios?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Claude-Code-Game-Studios take to install?
- 6.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Claude-Code-Game-Studios need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Claude-Code-Game-Studios?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Claude-Code-Game-Studios compare with the alternatives?
- Of the 19 ai-agents projects Argusic has installed and timed, Claude-Code-Game-Studios was the 11th fastest to reach a running state, and 12 of 19 reached one at all.
- Where is the evidence for Claude-Code-Game-Studios?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.