Claude-Code-Game-Studios

<p align="center"> <h1 align="center">Claude Code Game Studios</h1> <p align="center"> Turn a single Claude Code session into a full game development studio. <br /> 49 agents. 73 skills. One coordinated AI team. </p> </p> <p align="center"> <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="MIT License"></a> <a href=".claude/agents"><img src="https://img.shields.io/badge/agents-49-blueviolet" alt="49 Agents"></a> <a href=".claude/skills"><img src="https://img.shields.io/badge/skills-73-green" alt="73 Skills"></a> <a href=".claude/hooks"><img src="https://img.shields.io/badge/hooks-12-orange" alt="12 Hooks"></a> <a href=".claude/rules"><img src="https://img.shields.io/badge/rules-11-red" alt="11 Rules"></a> <a href="https://docs.anthropic.com/en/docs/claude-code"><img src="https://img.shields.io/badge/built%20for-Claude%20Code-f5f5f5?logo=anthropic" alt="Built for Claude Code"></a> <a href="https://www.buymeacoffee.com/donchitos3"><img src="https://img.shields.io/badge/Buy%20Me%20a%20Coffee-Support%20this%20project-FFDD00?logo=buymeacoffee&logoColor=black" alt="Buy Me a Coffee"></a> <a href="https://github.com/sponsors/Donchitos"><img src="https://img.shields.io/badge/GitHub%20Sponsors-Support%20this%20project-ea4aaa?logo=githubsponsors&logoColor=white" alt="GitHub Sponsors"></a> </p>

---

Why This Exists

Building a game solo with AI is powerful — but a single chat session has no structure. No one stops you from hardcoding magic numbers, skipping design docs, or writing spaghetti code. There's no QA pass, no design review, no one asking "does this actually fit the game's vision?"

Claude Code Game Studios solves this by giving your AI session the structure of a real studio. Instead of one general-purpose assistant, you get 49 specialized agents organized into a studio hierarchy — directors who guard the vision, department leads who own their domains, and specialists who do the hands-on work. Each agent has defined responsibilities, escalation paths, and quality gates.

The result: you still make every decision, but now you have a team that asks the right questions, catches mistakes early, and keeps your project organized from first brainstorm to launch.

---

Table of Contents

• What's Included
• Studio Hierarchy
• Slash Commands
• Getting Started
• Upgrading
• Project Structure
• How It Works
• Design Philosophy
• Customization
• Platform Support
• Community
• Supporting This Project
• License

---

What's Included

| Category | Count | Description | |----------|-------|-------------| | Agents | 49 | Specialized subagents across design, programming, art, audio, narrative, QA, and production | | Skills | 73 | Slash commands for every workflow phase (/start, /design-system, /create-epics, /create-stories, /dev-story, /story-done, etc.) | | Hooks | 12 | Automated validation on commits, pushes, asset changes, session lifecycle, agent audit trail, and gap detection | | Rules | 11 | Path-scoped coding standards enforced when editing gameplay, engine, AI, UI, network code, and more | | Templates | 41 | Document templates for GDDs, UX specs, ADRs, sprint plans, HUD design, accessibility, and more |

Studio Hierarchy

Agents are organized into three tiers, matching how real studios operate:

Tier 1 — Directors (Opus)
  creative-director    technical-director    producer

Tier 2 — Department Leads (Sonnet)
  game-designer        lead-programmer       art-director
  audio-director       narrative-director    qa-lead
  release-manager      localization-lead

Tier 3 — Specialists (Sonnet/Haiku)
  gameplay-programmer  engine-programmer     ai-programmer
  network-programmer   tools-programmer      ui-programmer
  systems-designer     level-designer        economy-designer
  technical-artist     sound-designer        writer
  world-builder        ux-designer           prototyper
  performance-analyst  devops-engineer       analytics-engineer
  security-engineer    qa-tester             accessibility-specialist
  live-ops-designer    community-manager

Engine Specialists

The template includes agent sets for all three major engines. Use the set that matches your project:

| Engine | Lead Agent | Sub-Specialists | |--------|-----------|-----------------| | Godot 4 | godot-specialist | GDScript, Shaders, GDExtension | | Unity | unity-specialist | DOTS/ECS, Shaders/VFX, Addressables, UI Toolkit | | Unreal Engine 5 | unreal-specialist | GAS, Blueprints, Replication, UMG/CommonUI |

Slash Commands

Type / in Claude Code to access all 73 skills:

Onboarding & Navigation /start /help /project-stage-detect /setup-engine /adopt

Game Design /brainstorm /map-systems /design-system /quick-design /review-all-gdds /propagate-design-change

Art & Assets /art-bible /asset-spec /asset-audit

UX & Interface Design /ux-design /ux-review

Architecture /create-architecture /architecture-decision /architecture-review /create-control-manifest

Stories & Sprints /create-epics /create-stories /dev-story /sprint-plan /sprint-status /story-readiness /story-done /estimate

Reviews & Analysis /design-review /code-review /balance-check /content-audit /scope-check /perf-profile /tech-debt /gate-check /consistency-check /security-audit

QA & Testing /qa-plan /smoke-check /soak-test /regression-suite /test-setup /test-helpers /test-evidence-review /test-flakiness /skill-test /skill-improve

Production /milestone-review /retrospective /bug-report /bug-triage /reverse-document /playtest-report

Release /release-checklist /launch-checklist /changelog /patch-notes /hotfix /day-one-patch

Creative & Content /prototype /onboard /localize

Team Orchestration (coordinate multiple agents on a single feature) /team-combat /team-narrative /team-ui /team-release /team-polish /team-audio /team-level /team-live-ops /team-qa

Getting Started

Prerequisites

• Git
• Claude Code (npm install -g @anthropic-ai/claude-code)
• Recommended: jq (for hook validation) and Python 3 (for JSON validation)

All hooks fail gracefully if optional tools are missing — nothing breaks, you just lose validation.

Setup

1. Clone or use as template:

   git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-game
   cd my-game
   

2. Open Claude Code and start a session:

   claude
   

3. Run /start — the system asks where you are (no idea, vague concept, clear design, existing work) and guides you to the right workflow. No assumptions.

   Or jump directly to a specific skill if you already know what you need:

   • /brainstorm — explore game ideas from scratch
   • /setup-engine godot 4.6 — configure your engine if you already know
   • /project-stage-detect — analyze an existing project

Upgrading

Already using an older version of this template? See UPGRADING.md for step-by-step migration instructions, a breakdown of what changed between versions, and which files are safe to overwrite vs. which need a manual merge.

Project Structure

CLAUDE.md                           # Master configuration
.claude/
  settings.json                     # Hooks, permissions, safety rules
  agents/                           # 49 agent definitions (markdown + YAML frontmatter)
  skills/                           # 73 slash commands (subdirectory per skill)
  hooks/                            # 12 hook scripts (bash, cross-platform)
  rules/                            # 11 path-scoped coding standards
  statusline.sh                     # Status line script (context%, model, stage, epic breadcrumb)
  docs/
    workflow-catalog.yaml           # 7-phase pipeline definition (read by /help)
    templates/                      # 41 document templates
src/                                # Game source code
assets/                             # Art, audio, VFX, shaders, data files
design/                             # GDDs, narrative docs, level designs
docs/                               # Technical documentation and ADRs
tests/                              # Test suites (unit, integration, performance, playtest)
tools/                              # Build and pipeline tools
prototypes/                         # Throwaway prototypes (isolated from src/)
production/                         # Sprint plans, milestones, release tracking

How It Works

Agent Coordination

Agents follow a structured delegation model:

1. Vertical delegation — directors delegate to leads, leads delegate to specialists
2. Horizontal consultation — same-tier agents can consult each other but can't make binding cross-domain decisions
3. Conflict resolution — disagreements escalate up to the shared parent (creative-director for design, technical-director for technical)
4. Change propagation — cross-department changes are coordinated by producer
5. Domain boundaries — agents don't modify files outside their domain without explicit delegation

Collaborative, Not Autonomous

This is not an auto-pilot system. Every agent follows a strict collaboration protocol:

1. Ask — agents ask questions before proposing solutions
2. Present options — agents show 2-4 options with pros/cons
3. You decide — the user always makes the call
4. Draft — agents show work before finalizing
5. Approve — nothing gets written without your sign-off

You stay in control. The agents provide structure and expertise, not autonomy.

Automated Safety

Hooks run automatically on every session:

| Hook | Trigger | What It Does | |------|---------|--------------| | validate-commit.sh | PreToolUse (Bash) | Checks for hardcoded values, TODO format, JSON validity, design doc sections — exits early if the command is not git commit | | validate-push.sh | PreToolUse (Bash) | Warns on pushes to protected branches — exits early if the command is not git push | | validate-assets.sh | PostToolUse (Write/Edit) | Validates naming conventions and JSON structure — exits early if the file is not in assets/ | | session-start.sh | Session open | Shows current branch and recent commits for orientation | | detect-gaps.sh | Session open | Detects fresh projects (suggests /start) and missing design docs when code or prototypes exist | | pre-compact.sh | Before compaction | Preserves session progress notes | | post-compact.sh | After compaction | Reminds Claude to restore session state from active.md | | notify.sh | Notification event | Shows Windows toast notification via PowerShell | | session-stop.sh | Session close | Archives active.md to session log and records git activity | | log-agent.sh | Agent spawned | Audit trail start — logs subagent invocation | | log-agent-stop.sh | Agent stops | Audit trail stop — completes subagent record | | validate-skill-change.sh | PostToolUse (Write/Edit) | Advises running /skill-test after any .claude/skills/ change |

Note: validate-commit.sh, validate-assets.sh, and validate-skill-change.sh fire on every Bash/Write tool call and exit immediately (exit 0) when the command or file path is not relevant. This is normal hook behavior — not a performance concern.

Permission rules in settings.json auto-allow safe operations (git status, test runs) and block dangerous ones (force push, rm -rf, reading `.env