Claude Code Game Studios is a setup that organizes Claude Code into a coordinated game-development team of specialized AI agents. It supports game projects across design, programming, art, audio, narrative, quality assurance, and production, with skills and workflows for coordinating that work.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Donchitos/Claude-Code-Game-Studios --skill ux-reviewgit clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-StudiosWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/donchitos/claude-code-game-studios/ux-review)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/ux-review"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/ux-review.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 7 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00051 | $0.02447 |
| Opus 5 | $0.00026 | $0.01223 |
| Sonnet 5 | $0.00010 | $0.00489 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
ux-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- ux-review — 94% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Validates UX design documents before they enter the implementation pipeline.
Acts as the quality gate between UX Design and Visual Design/Implementation in
the /team-ui pipeline.
Run this skill:
- After completing a UX spec with
/ux-design - Before handing off to
ui-programmerorart-director - Before the Pre-Production to Production gate check (which requires key screens to have reviewed UX specs)
- After major revisions to a UX spec
Verdict levels:
- APPROVED — spec is complete, consistent, and implementation-ready
- NEEDS REVISION — specific gaps found; fix before handoff but not a full redesign
- MAJOR REVISION NEEDED — fundamental issues with scope, player need, or completeness; needs significant rework
Phase 1: Parse Arguments
- Specific file path (e.g.,
/ux-review design/ux/inventory.md): validate that one document all: find all files indesign/ux/and validate eachhud: validatedesign/ux/hud.mdspecificallypatterns: validatedesign/ux/interaction-patterns.mdspecifically- No argument: ask the user which spec to validate
For all, output a summary table first (file | verdict | primary issue) then
full detail for each.
Phase 2: Load Cross-Reference Context
Before validating any spec, load:
- Input & Platform config: Read
.claude/docs/technical-preferences.mdand extract## Input & Platform. This is the authoritative source for which input methods the game supports — use it to drive the Input Method Coverage checks in Phase 3A, not the spec's own header. If unconfigured, fall back to the spec header. - The accessibility tier committed to in
design/accessibility-requirements.md(if it exists) - The interaction pattern library at
design/ux/interaction-patterns.md(if it exists) - The GDDs referenced in the spec's header (read their UI Requirements sections)
- The player journey map at
design/player-journey.md(if it exists) for context-arrival validation
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 264 lines · 51 tokens per session scan A 1dd5a719efd1
ux-review is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,880 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 2,447 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
flame-harness-design
Phase 3 — define the Flutter designtokens.dart spec (palette, typography, spacing), the game's art/visual concept, and the asset/audio sourcing plan.
unity-ui
Use when building user interfaces — UI Toolkit vs uGUI decisions, layout strategies, dialog systems, responsive UI, data binding, and HUD architecture.
difficulty-and-balancing
Use when designing, tuning, or reviewing the difficulty or balance of any game system — encounter tuning, cost curves, dominant-strategy audits, dynamic difficulty adjustment (DDA), difficulty settings, and accessibility assists. Also use to diagnose "this is too hard/too easy", "everything feels overpowered", a…
onboarding-and-teaching
Use when designing, reviewing, or generating the introduction to ANY mechanic in ANY genre — the four-beat teaching pattern (introduce→test→combine→twist), show-don't-tell level design, progressive disclosure and scaffolding, the mechanic dependency graph, FTUE (first-time user experience), early retention funnels…
ui-ux-and-feedback
Use when designing, auditing, or generating a HUD, menu system, or feedback vocabulary for any genre — information hierarchy, diegetic vs. non-diegetic classification, cognitive load budgeting, feedback channel design, menu flow, input modality, and accessibility. Also use to diagnose a UI that is cluttered, that…
game-accessibility-specialist
Invoke when the user asks about accessibility, inclusive design, colorblind mode, remappable controls, screen reader support, EAA compliance, CVAA, difficulty options, motor accommodations, or one-handed mode. Triggers on: "accessibility", "inclusive design", "colorblind", "remappable controls", "screen reader"…