Donchitos/Claude-Code-Game-Studios▌

Turn a single Claude Code session into a full game development studio with 49 agents and 72 skills.

### Localize - description: "Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO - argument-hint: "[scan|extract|validate|status|brief|cultural-review|vo-pipeline|rtl-check|freeze|qa]" - agent: localization-lead

### Code Review - description: "Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testabili - argument-hint: "[path-to-file-or-directory]" - allowed-tools: Read, Glob, Grep, Bash, Task

### Art Bible - description: "Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or an - argument-hint: "[--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion

### Balance Check - description: "Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-re - argument-hint: "[system-name|path-to-data-file]" - allowed-tools: Read, Glob, Grep

### Tech Debt - description: "Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling." - argument-hint: "[scan|add|prioritize|report]" - allowed-tools: Read, Glob, Grep, Write

### Test Helpers - description: "Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and moc - argument-hint: "[system-name | all | scaffold]" - allowed-tools: Read, Glob, Grep, Write

### Team Release - description: "Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment." - argument-hint: "[version number or 'next']" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Test Setup - description: "Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. R - argument-hint: "[force]" - allowed-tools: Read, Glob, Grep, Bash, Write

### Team Ui - description: "Orchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio - argument-hint: "[UI feature description]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Test Evidence Review - name: test-evidence-review - description: "Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness - argument-hint: "[story-path | sprint | system-name]"

### Ux Design - description: "Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec. - argument-hint: "[screen/flow name] or 'hud' or 'patterns'" - allowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion, Task

### Team Narrative - description: "Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design. - argument-hint: "[narrative content description]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion, TodoWrite

### Team Qa - description: "Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a - argument-hint: "[sprint | feature: system-name]" - allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion

### Ux Review - description: "Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISIO - argument-hint: "[file-path or 'all' or 'hud' or 'patterns']" - allowed-tools: Read, Glob, Grep

### Test Flakiness - description: "Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and - argument-hint: "[ci-log-path | scan | registry]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash

### Project Stage Detect - name: project-stage-detect - description: "Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are - argument-hint: "[optional: role filter like 'programmer' or 'designer']"

### Sprint Status - description: "Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any ti - argument-hint: "[sprint-number or blank for current]" - allowed-tools: Read, Glob, Grep

### Qa Plan - description: "Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering a - argument-hint: "[sprint | feature: system-name | story: path]" - allowed-tools: Read, Glob, Grep, Write, AskUserQuestion

### Soak Test - description: "Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that - argument-hint: "[duration: 30m | 1h | 2h | 4h] [focus: memory | stability | balance | all]" - allowed-tools: Read, Glob, Grep, Write

### Design System - description: "Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, - argument-hint: "<system-name> [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion, TodoWrite

### Playtest Report - name: playtest-report - description: "Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis." - argument-hint: "[new|analyze path-to-notes] [--review full|lean|solo]"

### Security Audit - description: "Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remedi - argument-hint: "[full | network | save | input | quick]" - allowed-tools: Read, Glob, Grep, Bash, Write, Task

### Start - description: "First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions." - argument-hint: "[no arguments]" - allowed-tools: Read, Glob, Grep, Write, AskUserQuestion

### Quick Design - description: "Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to w - argument-hint: "[brief description of the change]" - allowed-tools: Read, Glob, Grep, Write, Edit

### Map Systems - description: "Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index." - argument-hint: "[next | system-name] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion, TodoWrite, Task

### Release Checklist - name: release-checklist - description: "Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness." - argument-hint: "[platform: pc|console|mobile|all]"

### Sprint Plan - description: "Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs - argument-hint: "[new|update|status] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion

### Milestone Review - name: milestone-review - description: "Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when ev - argument-hint: "[milestone-name|current] [--review full|lean|solo]"

### Skill Test - description: "Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report)." - argument-hint: "static [skill-name | all] | spec [skill-name] | category [skill-name | all] | audit" - allowed-tools: Read, Glob, Grep, Write

### Team Combat - description: "Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat fe - argument-hint: "[combat feature description]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Team Polish - description: "Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality." - argument-hint: "[feature or area to polish]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Story Readiness - name: story-readiness - description: "Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces - argument-hint: "[story-file-path or 'all' or 'sprint']"

### Patch Notes - description: "Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication." - argument-hint: "[version] [--style brief|detailed|full]" - allowed-tools: Read, Glob, Grep, Write, Bash

### Team Audio - description: "Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation." - argument-hint: "[feature or area to design audio for]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Launch Checklist - name: launch-checklist - description: "Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs." - argument-hint: "[launch-date or 'dry-run']"

### Prototype - description: "Rapid prototyping workflow. Skips normal standards to quickly validate a game concept or mechanic. Produces throwaway code and a structured prototype report." - argument-hint: "[concept-description] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task

### Retrospective - description: "Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration." - argument-hint: "[sprint-N|milestone-name]" - allowed-tools: Read, Glob, Grep, Write

### Setup Engine - description: "Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LL - argument-hint: "[engine] | [engine version] | refresh | upgrade [old-version] [new-version] | no args for guided selection" - allowed-tools: Read, Glob, Grep, Write, Edit, WebSearch, WebFetch, Task, AskUserQuestion

### Onboard - description: "Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the - argument-hint: "[role|area]" - allowed-tools: Read, Glob, Grep, Write

### Propagate Design Change - name: propagate-design-change - description: "When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user - argument-hint: "[path/to/changed-gdd.md]"

### Reverse Document - name: reverse-document - description: "Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs." - argument-hint: "<type> <path> (e.g., 'design src/gameplay/combat' or 'architecture src/core')"

### Gate Check - description: "Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to - argument-hint: "[target-phase: systems-design | technical-setup | pre-production | production | polish | release] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Bash, Write, Task, AskUserQuestion

### Regression Suite - name: regression-suite - description: "Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementi - argument-hint: "[update | audit | report]"

### Team Level - description: "Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation." - argument-hint: "[level name or area to design]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Skill Improve - description: "Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change." - argument-hint: "[skill-name]" - allowed-tools: Read, Glob, Grep, Write, Bash

### Review All Gdds - name: review-all-gdds - description: "Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, ownership conflicts, formula inc - argument-hint: "[focus: full | consistency | design-theory | since-last-review]"

### Perf Profile - description: "Structured performance profiling workflow. Identifies bottlenecks, measures against budgets, and generates optimization recommendations with priority rankings." - argument-hint: "[system-name or 'full']" - agent: performance-analyst

### Story Done - description: "End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story sta - argument-hint: "[story-file-path] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Bash, Edit, AskUserQuestion, Task

### Smoke Check - description: "Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories ar - argument-hint: "[sprint | quick | --platform pc|console|mobile|all]" - allowed-tools: Read, Glob, Grep, Bash, Write, AskUserQuestion

### Scope Check - description: "Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope cr - argument-hint: "[feature-name or sprint-N]" - allowed-tools: Read, Glob, Grep, Bash

### Team Live Ops - description: "Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to - argument-hint: "[season name or event description]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Consistency Check - name: consistency-check - description: "Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variabl - argument-hint: "[full | since-last-review | entity:<name> | item:<name>]"

### Dev Story - description: "Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, imp - argument-hint: "[story-path]" - allowed-tools: Read, Glob, Grep, Write, Bash, Task, AskUserQuestion

### Changelog - description: "Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions." - argument-hint: "[version|sprint-number]" - allowed-tools: Read, Glob, Grep, Bash, Write

### Create Control Manifest - name: create-control-manifest - description: "After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted A - argument-hint: "[update — regenerate from current ADRs]"

### Help - description: "Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now or I'm stuck or I don't know what to do" - argument-hint: "[optional: what you just finished, e.g. 'finished design-review' or 'stuck on ADRs']" - allowed-tools: Read, Glob, Grep

### Estimate - description: "Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels." - argument-hint: "[task-description]" - allowed-tools: Read, Glob, Grep

### Create Epics - description: "Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories - argument-hint: "[system-name | layer: foundation|core|feature|presentation | all] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion

### Design Review - description: "Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programme - argument-hint: "[path-to-design-doc] [--depth full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion

### Create Stories - description: "Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance c - argument-hint: "[epic-slug | epic-path] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion

### Create Architecture - name: create-architecture - description: "Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a com - argument-hint: "[focus-area: full | layers | data-flow | api-boundaries | adr-audit] [--review full|lean|solo]"

### Content Audit - description: "Audit GDD-specified content counts against implemented content. Identifies what's planned vs built." - argument-hint: "[system-name | --summary | (no arg = full audit)]" - allowed-tools: Read, Glob, Grep, Write

### Hotfix - description: "Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly." - argument-hint: "[bug-id or description]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task

### Day One Patch - description: "Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately af - argument-hint: "[scope: known-bugs | cert-feedback | all]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion

### Asset Spec - description: "Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run - argument-hint: "[system:<name> | level:<name> | character:<name>] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion

### Asset Audit - description: "Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard vi - argument-hint: "[category|all]" - allowed-tools: Read, Glob, Grep

### Architecture Decision - name: architecture-decision - description: "Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should ha - argument-hint: "[title] [--review full|lean|solo]"

### Bug Triage - description: "Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug - argument-hint: "[sprint | full | trend]" - allowed-tools: Read, Glob, Grep, Write, Edit

### Bug Report - description: "Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context." - argument-hint: "[description] | analyze [path-to-file]" - allowed-tools: Read, Glob, Grep, Write

### Adopt - description: "Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this - argument-hint: "[focus: full | gdds | adrs | stories | infra]" - allowed-tools: Read, Glob, Grep, Write, AskUserQuestion

### Architecture Review - name: architecture-review - description: "Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gap - argument-hint: "[focus: full | coverage | consistency | engine | single-gdd path/to/gdd.md]"

### Brainstorm - description: "Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative e - argument-hint: "[genre or theme hint, or 'open'] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, WebSearch, Task, AskUserQuestion