Skip to content
Navigation Menu
Platform
Solutions
Resources
Open Source
Enterprise
Pricing
Sign in
Sign up
Donchitos
/
Claude-Code-Game-Studios
Public template
Code
Issues
8
Pull requests
Discussions
Actions
Projects
Security and quality
Insights
Donchitos/Claude-Code-Game-Studios
Name
Donchitosclaude
Donchitos
and
claude
Fix log-agent hooks reading wrong field — audit trail always logged "…
666e0fc
·
last week
.claude
Fix log-agent hooks reading wrong field — audit trail always logged "…
last week
.github
Update FUNDING.yml: GitHub Sponsors + Buy Me a Coffee (remove ko-fi)
last week
CCGS Skill Testing Framework
Prep v1 beta release: fix stale refs, counts, and add sponsorship links
last week
design
Release v0.4.0: /consistency-check, skill fixes, genre-agnostic agents
3 weeks ago
docs
Add gate intensity modes: full, lean, and solo review control
3 weeks ago
production/session-state
Release v0.2.0: Context Resilience, AskUserQuestion, /design-systems
2 months ago
src
Add notification hook, directory CLAUDE.md scaffolding
last month
.gitignore
Add v0.6.0: full skill/agent QA pass, 3 new agents tested, template c…
last week
CLAUDE.md
Release v0.2.0: Context Resilience, AskUserQuestion, /design-systems
2 months ago
LICENSE
Game Studio Agent Architecture — complete setup (Phases 1-7)
2 months ago
README.md
Prep v1 beta release: fix stale refs, counts, and add sponsorship links
last week
UPGRADING.md
Add v0.5.0: CCGS Skill Testing Framework, skill-improve, 4 new skills…
last week
Repository files navigation
README
MIT license
Claude Code Game Studios
Turn a single Claude Code session into a full game development studio.
49 agents. 72 skills. One coordinated AI team.
MIT License 49 Agents 72 Skills 12 Hooks 11 Rules Built for Claude Code Buy Me a Coffee GitHub Sponsors
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 72 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 39 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 72 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
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
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
Clone or use as template:
git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git my-game
cd my-game
Open Claude Code and start a session:
claude
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/ # 72 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/ # 39 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:
Vertical delegation — directors delegate to leads, leads delegate to specialists
Horizontal consultation — same-tier agents can consult each other but can't make binding cross-domain decisions
Conflict resolution — disagreements escalate up to the shared parent (creative-director for design, technical-director for technical)
Change propagation — cross-department changes are coordinated by producer
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:
Ask — agents ask questions before proposing solutions
Present options — agents show 2-4 options with pros/cons
You decide — the user always makes the call
Draft — agents show work before finalizing
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 files).
Path-Scoped Rules
Coding standards are automatically enforced based on file location:
Path Enforces
src/gameplay/** Data-driven values, delta time usage, no UI references
src/core/** Zero allocations in hot paths, thread safety, API stability
src/ai/** Performance budgets, debuggability, data-driven parameters
src/networking/** Server-authoritative, versioned messages, security
src/ui/** No game state ownership, localization-ready, accessibility
design/gdd/** Required 8 sections, formula format, edge cases
tests/** Test naming, coverage requirements, fixture patterns
prototypes/** Relaxed standards, README required, hypothesis documented
Design Philosophy
This template is grounded in professional game development practices:
MDA Framework — Mechanics, Dynamics, Aesthetics analysis for game design
Self-Determination Theory — Autonomy, Competence, Relatedness for player motivation
Flow State Design — Challenge-skill balance for player engagement
Bartle Player Types — Audience targeting and validation
Verification-Driven Development — Tests first, then implementation
Customization
This is a template, not a locked framework. Everything is meant to be customized:
Add/remove agents — delete agent files you don't need, add new ones for your domains
Edit agent prompts — tune agent behavior, add project-specific knowledge
Modify skills — adjust workflows to match your team's process
Add rules — create new path-scoped rules for your project's directory structure
Tune hooks — adjust validation strictness, add new checks
Pick your engine — use the Godot, Unity, or Unreal agent set (or none)
Set review intensity — full (all director gates), lean (phase gates only), or solo (none). Set during /start or edit production/review-mode.txt. Override per-run with --review solo on any skill.
Platform Support
Tested on Windows 10 with Git Bash. All hooks use POSIX-compatible patterns (grep -E, not grep -P) and include fallbacks for missing tools. Works on macOS and Linux without modification.
Community
Discussions — GitHub Discussions for questions, ideas, and showcasing what you've built
Issues — Bug reports and feature requests
Supporting This Project
Claude Code Game Studios is free and open source. If it saves you time or helps you ship your game, consider supporting continued development:
Buy Me a Coffee GitHub Sponsors
Buy Me a Coffee — one-time support
GitHub Sponsors — recurring support through GitHub
Sponsorships help fund time spent maintaining skills, adding new agents, keeping up with Claude Code and engine API changes, and responding to community issues.
Built for Claude Code. Maintained and extended — contributions welcome via GitHub Discussions.
License
MIT License. See LICENSE for details.
About
Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Topics
gamedev unity game-development godot unreal-engine game-design ai-agents claude indie-game-dev ai-assisted-development anthropic claude-code
Resources
Readme
License
MIT license
Activity
Stars
10.7k stars
Watchers
122 watching
Forks
1.6k forks
Report repository
Releases 4
v1.0.0-beta — Claude Code Game Studios
Latest
last week
- 3 releases
Sponsor this project
@Donchitos
Donchitos
buy_me_a_coffee
buymeacoffee.com/donchitos3
Learn more about GitHub Sponsors
Packages
No packages published
Contributors
2
@Donchitos
Donchitos
@claude
claude Claude
Languages
Shell
100.0%
Footer
© 2026 GitHub, Inc.
Footer navigation
Terms
Privacy
Security
Status
Community
Docs
Contact
Manage cookies
Do not share my personal information
https://github.com/Donchitos/Claude-Code-Game-Studios
