[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-74852":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":38,"readmeContent":39,"aiSummary":40,"trendingCount":16,"starSnapshotCount":16,"syncStatus":41,"lastSyncTime":42,"discoverSource":43},74852,"Claude-Code-Game-Studios","Donchitos\u002FClaude-Code-Game-Studios","Donchitos","Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.","",null,"Shell",21367,3105,162,25,0,355,890,1653,1065,120,"MIT License",false,"main",[26,27,28,29,30,31,32,33,34,35,36,37],"ai-agents","ai-assisted-development","anthropic","claude","claude-code","game-design","game-development","gamedev","godot","indie-game-dev","unity","unreal-engine","2026-06-12 04:01:16","\u003Cp align=\"center\">\n  \u003Ch1 align=\"center\">Claude Code Game Studios\u003C\u002Fh1>\n  \u003Cp align=\"center\">\n    Turn a single Claude Code session into a full game development studio.\n    \u003Cbr \u002F>\n    49 agents. 73 skills. One coordinated AI team.\n  \u003C\u002Fp>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"LICENSE\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-blue.svg\" alt=\"MIT License\">\u003C\u002Fa>\n  \u003Ca href=\".claude\u002Fagents\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fagents-49-blueviolet\" alt=\"49 Agents\">\u003C\u002Fa>\n  \u003Ca href=\".claude\u002Fskills\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fskills-73-green\" alt=\"73 Skills\">\u003C\u002Fa>\n  \u003Ca href=\".claude\u002Fhooks\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fhooks-12-orange\" alt=\"12 Hooks\">\u003C\u002Fa>\n  \u003Ca href=\".claude\u002Frules\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Frules-11-red\" alt=\"11 Rules\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fdocs.anthropic.com\u002Fen\u002Fdocs\u002Fclaude-code\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fbuilt%20for-Claude%20Code-f5f5f5?logo=anthropic\" alt=\"Built for Claude Code\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fwww.buymeacoffee.com\u002Fdonchitos3\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FBuy%20Me%20a%20Coffee-Support%20this%20project-FFDD00?logo=buymeacoffee&logoColor=black\" alt=\"Buy Me a Coffee\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsponsors\u002FDonchitos\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FGitHub%20Sponsors-Support%20this%20project-ea4aaa?logo=githubsponsors&logoColor=white\" alt=\"GitHub Sponsors\">\u003C\u002Fa>\n\u003C\u002Fp>\n\n---\n\n## Why This Exists\n\nBuilding 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?\"\n\n**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.\n\nThe 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.\n\n---\n\n## Table of Contents\n\n- [What's Included](#whats-included)\n- [Studio Hierarchy](#studio-hierarchy)\n- [Slash Commands](#slash-commands)\n- [Getting Started](#getting-started)\n- [Upgrading](#upgrading)\n- [Project Structure](#project-structure)\n- [How It Works](#how-it-works)\n- [Design Philosophy](#design-philosophy)\n- [Customization](#customization)\n- [Platform Support](#platform-support)\n- [Community](#community)\n- [Supporting This Project](#supporting-this-project)\n- [License](#license)\n\n---\n\n## What's Included\n\n| Category | Count | Description |\n|----------|-------|-------------|\n| **Agents** | 49 | Specialized subagents across design, programming, art, audio, narrative, QA, and production |\n| **Skills** | 73 | Slash commands for every workflow phase (`\u002Fstart`, `\u002Fdesign-system`, `\u002Fcreate-epics`, `\u002Fcreate-stories`, `\u002Fdev-story`, `\u002Fstory-done`, etc.) |\n| **Hooks** | 12 | Automated validation on commits, pushes, asset changes, session lifecycle, agent audit trail, and gap detection |\n| **Rules** | 11 | Path-scoped coding standards enforced when editing gameplay, engine, AI, UI, network code, and more |\n| **Templates** | 41 | Document templates for GDDs, UX specs, ADRs, sprint plans, HUD design, accessibility, and more |\n\n## Studio Hierarchy\n\nAgents are organized into three tiers, matching how real studios operate:\n\n```\nTier 1 — Directors (Opus)\n  creative-director    technical-director    producer\n\nTier 2 — Department Leads (Sonnet)\n  game-designer        lead-programmer       art-director\n  audio-director       narrative-director    qa-lead\n  release-manager      localization-lead\n\nTier 3 — Specialists (Sonnet\u002FHaiku)\n  gameplay-programmer  engine-programmer     ai-programmer\n  network-programmer   tools-programmer      ui-programmer\n  systems-designer     level-designer        economy-designer\n  technical-artist     sound-designer        writer\n  world-builder        ux-designer           prototyper\n  performance-analyst  devops-engineer       analytics-engineer\n  security-engineer    qa-tester             accessibility-specialist\n  live-ops-designer    community-manager\n```\n\n### Engine Specialists\n\nThe template includes agent sets for all three major engines. Use the set that matches your project:\n\n| Engine | Lead Agent | Sub-Specialists |\n|--------|-----------|-----------------|\n| **Godot 4** | `godot-specialist` | GDScript, Shaders, GDExtension |\n| **Unity** | `unity-specialist` | DOTS\u002FECS, Shaders\u002FVFX, Addressables, UI Toolkit |\n| **Unreal Engine 5** | `unreal-specialist` | GAS, Blueprints, Replication, UMG\u002FCommonUI |\n\n## Slash Commands\n\nType `\u002F` in Claude Code to access all 73 skills:\n\n**Onboarding & Navigation**\n`\u002Fstart` `\u002Fhelp` `\u002Fproject-stage-detect` `\u002Fsetup-engine` `\u002Fadopt`\n\n**Game Design**\n`\u002Fbrainstorm` `\u002Fmap-systems` `\u002Fdesign-system` `\u002Fquick-design` `\u002Freview-all-gdds` `\u002Fpropagate-design-change`\n\n**Art & Assets**\n`\u002Fart-bible` `\u002Fasset-spec` `\u002Fasset-audit`\n\n**UX & Interface Design**\n`\u002Fux-design` `\u002Fux-review`\n\n**Architecture**\n`\u002Fcreate-architecture` `\u002Farchitecture-decision` `\u002Farchitecture-review` `\u002Fcreate-control-manifest`\n\n**Stories & Sprints**\n`\u002Fcreate-epics` `\u002Fcreate-stories` `\u002Fdev-story` `\u002Fsprint-plan` `\u002Fsprint-status` `\u002Fstory-readiness` `\u002Fstory-done` `\u002Festimate`\n\n**Reviews & Analysis**\n`\u002Fdesign-review` `\u002Fcode-review` `\u002Fbalance-check` `\u002Fcontent-audit` `\u002Fscope-check` `\u002Fperf-profile` `\u002Ftech-debt` `\u002Fgate-check` `\u002Fconsistency-check` `\u002Fsecurity-audit`\n\n**QA & Testing**\n`\u002Fqa-plan` `\u002Fsmoke-check` `\u002Fsoak-test` `\u002Fregression-suite` `\u002Ftest-setup` `\u002Ftest-helpers` `\u002Ftest-evidence-review` `\u002Ftest-flakiness` `\u002Fskill-test` `\u002Fskill-improve`\n\n**Production**\n`\u002Fmilestone-review` `\u002Fretrospective` `\u002Fbug-report` `\u002Fbug-triage` `\u002Freverse-document` `\u002Fplaytest-report`\n\n**Release**\n`\u002Frelease-checklist` `\u002Flaunch-checklist` `\u002Fchangelog` `\u002Fpatch-notes` `\u002Fhotfix` `\u002Fday-one-patch`\n\n**Creative & Content**\n`\u002Fprototype` `\u002Fonboard` `\u002Flocalize`\n\n**Team Orchestration** (coordinate multiple agents on a single feature)\n`\u002Fteam-combat` `\u002Fteam-narrative` `\u002Fteam-ui` `\u002Fteam-release` `\u002Fteam-polish` `\u002Fteam-audio` `\u002Fteam-level` `\u002Fteam-live-ops` `\u002Fteam-qa`\n\n## Getting Started\n\n### Prerequisites\n\n- [Git](https:\u002F\u002Fgit-scm.com\u002F)\n- [Claude Code](https:\u002F\u002Fdocs.anthropic.com\u002Fen\u002Fdocs\u002Fclaude-code) (`npm install -g @anthropic-ai\u002Fclaude-code`)\n- **Recommended**: [jq](https:\u002F\u002Fjqlang.github.io\u002Fjq\u002F) (for hook validation) and Python 3 (for JSON validation)\n\nAll hooks fail gracefully if optional tools are missing — nothing breaks, you just lose validation.\n\n### Setup\n\n1. **Clone or use as template**:\n   ```bash\n   git clone https:\u002F\u002Fgithub.com\u002FDonchitos\u002FClaude-Code-Game-Studios.git my-game\n   cd my-game\n   ```\n\n2. **Open Claude Code** and start a session:\n   ```bash\n   claude\n   ```\n\n3. **Run `\u002Fstart`** — the system asks where you are (no idea, vague concept,\n   clear design, existing work) and guides you to the right workflow. No assumptions.\n\n   Or jump directly to a specific skill if you already know what you need:\n   - `\u002Fbrainstorm` — explore game ideas from scratch\n   - `\u002Fsetup-engine godot 4.6` — configure your engine if you already know\n   - `\u002Fproject-stage-detect` — analyze an existing project\n\n## Upgrading\n\nAlready using an older version of this template? See [UPGRADING.md](UPGRADING.md)\nfor step-by-step migration instructions, a breakdown of what changed between\nversions, and which files are safe to overwrite vs. which need a manual merge.\n\n## Project Structure\n\n```\nCLAUDE.md                           # Master configuration\n.claude\u002F\n  settings.json                     # Hooks, permissions, safety rules\n  agents\u002F                           # 49 agent definitions (markdown + YAML frontmatter)\n  skills\u002F                           # 73 slash commands (subdirectory per skill)\n  hooks\u002F                            # 12 hook scripts (bash, cross-platform)\n  rules\u002F                            # 11 path-scoped coding standards\n  statusline.sh                     # Status line script (context%, model, stage, epic breadcrumb)\n  docs\u002F\n    workflow-catalog.yaml           # 7-phase pipeline definition (read by \u002Fhelp)\n    templates\u002F                      # 41 document templates\nsrc\u002F                                # Game source code\nassets\u002F                             # Art, audio, VFX, shaders, data files\ndesign\u002F                             # GDDs, narrative docs, level designs\ndocs\u002F                               # Technical documentation and ADRs\ntests\u002F                              # Test suites (unit, integration, performance, playtest)\ntools\u002F                              # Build and pipeline tools\nprototypes\u002F                         # Throwaway prototypes (isolated from src\u002F)\nproduction\u002F                         # Sprint plans, milestones, release tracking\n```\n\n## How It Works\n\n### Agent Coordination\n\nAgents follow a structured delegation model:\n\n1. **Vertical delegation** — directors delegate to leads, leads delegate to specialists\n2. **Horizontal consultation** — same-tier agents can consult each other but can't make binding cross-domain decisions\n3. **Conflict resolution** — disagreements escalate up to the shared parent (`creative-director` for design, `technical-director` for technical)\n4. **Change propagation** — cross-department changes are coordinated by `producer`\n5. **Domain boundaries** — agents don't modify files outside their domain without explicit delegation\n\n### Collaborative, Not Autonomous\n\nThis is **not** an auto-pilot system. Every agent follows a strict collaboration protocol:\n\n1. **Ask** — agents ask questions before proposing solutions\n2. **Present options** — agents show 2-4 options with pros\u002Fcons\n3. **You decide** — the user always makes the call\n4. **Draft** — agents show work before finalizing\n5. **Approve** — nothing gets written without your sign-off\n\nYou stay in control. The agents provide structure and expertise, not autonomy.\n\n### Automated Safety\n\n**Hooks** run automatically on every session:\n\n| Hook | Trigger | What It Does |\n|------|---------|--------------|\n| `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` |\n| `validate-push.sh` | PreToolUse (Bash) | Warns on pushes to protected branches — exits early if the command is not `git push` |\n| `validate-assets.sh` | PostToolUse (Write\u002FEdit) | Validates naming conventions and JSON structure — exits early if the file is not in `assets\u002F` |\n| `session-start.sh` | Session open | Shows current branch and recent commits for orientation |\n| `detect-gaps.sh` | Session open | Detects fresh projects (suggests `\u002Fstart`) and missing design docs when code or prototypes exist |\n| `pre-compact.sh` | Before compaction | Preserves session progress notes |\n| `post-compact.sh` | After compaction | Reminds Claude to restore session state from `active.md` |\n| `notify.sh` | Notification event | Shows Windows toast notification via PowerShell |\n| `session-stop.sh` | Session close | Archives `active.md` to session log and records git activity |\n| `log-agent.sh` | Agent spawned | Audit trail start — logs subagent invocation |\n| `log-agent-stop.sh` | Agent stops | Audit trail stop — completes subagent record |\n| `validate-skill-change.sh` | PostToolUse (Write\u002FEdit) | Advises running `\u002Fskill-test` after any `.claude\u002Fskills\u002F` change |\n\n> **Note**: `validate-commit.sh`, `validate-assets.sh`, and `validate-skill-change.sh` fire on every Bash\u002FWrite 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.\n\n**Permission rules** in `settings.json` auto-allow safe operations (git status, test runs) and block dangerous ones (force push, `rm -rf`, reading `.env` files).\n\n### Path-Scoped Rules\n\nCoding standards are automatically enforced based on file location:\n\n| Path | Enforces |\n|------|----------|\n| `src\u002Fgameplay\u002F**` | Data-driven values, delta time usage, no UI references |\n| `src\u002Fcore\u002F**` | Zero allocations in hot paths, thread safety, API stability |\n| `src\u002Fai\u002F**` | Performance budgets, debuggability, data-driven parameters |\n| `src\u002Fnetworking\u002F**` | Server-authoritative, versioned messages, security |\n| `src\u002Fui\u002F**` | No game state ownership, localization-ready, accessibility |\n| `design\u002Fgdd\u002F**` | Required 8 sections, formula format, edge cases |\n| `tests\u002F**` | Test naming, coverage requirements, fixture patterns |\n| `prototypes\u002F**` | Relaxed standards, README required, hypothesis documented |\n\n## Design Philosophy\n\nThis template is grounded in professional game development practices:\n\n- **MDA Framework** — Mechanics, Dynamics, Aesthetics analysis for game design\n- **Self-Determination Theory** — Autonomy, Competence, Relatedness for player motivation\n- **Flow State Design** — Challenge-skill balance for player engagement\n- **Bartle Player Types** — Audience targeting and validation\n- **Verification-Driven Development** — Tests first, then implementation\n\n## Customization\n\nThis is a **template**, not a locked framework. Everything is meant to be customized:\n\n- **Add\u002Fremove agents** — delete agent files you don't need, add new ones for your domains\n- **Edit agent prompts** — tune agent behavior, add project-specific knowledge\n- **Modify skills** — adjust workflows to match your team's process\n- **Add rules** — create new path-scoped rules for your project's directory structure\n- **Tune hooks** — adjust validation strictness, add new checks\n- **Pick your engine** — use the Godot, Unity, or Unreal agent set (or none)\n- **Set review intensity** — `full` (all director gates), `lean` (phase gates only), or `solo` (none). Set during `\u002Fstart` or edit `production\u002Freview-mode.txt`. Override per-run with `--review solo` on any skill.\n\n## Platform Support\n\nPrimary development and testing on **Windows 10** with Git Bash. All hooks use POSIX-compatible patterns (`grep -E`, not `grep -P`) and include fallbacks for missing tools, so they should run on macOS and Linux. The `notify.sh` hook uses PowerShell for Windows toast notifications and is a no-op elsewhere — desktop notifications on macOS\u002FLinux are not yet wired. Cross-platform testing is ongoing; please file issues for any platform-specific breakage.\n\n## Community\n\n- **Discussions** — [GitHub Discussions](https:\u002F\u002Fgithub.com\u002FDonchitos\u002FClaude-Code-Game-Studios\u002Fdiscussions) for questions, ideas, and showcasing what you've built\n- **Issues** — [Bug reports and feature requests](https:\u002F\u002Fgithub.com\u002FDonchitos\u002FClaude-Code-Game-Studios\u002Fissues)\n\n---\n\n## Supporting This Project\n\nClaude Code Game Studios is free and open source. If it saves you time or helps you ship your game, consider supporting continued development:\n\n\u003Cp>\n  \u003Ca href=\"https:\u002F\u002Fwww.buymeacoffee.com\u002Fdonchitos3\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FBuy%20Me%20a%20Coffee-FFDD00?style=for-the-badge&logo=buy-me-a-coffee&logoColor=black\" alt=\"Buy Me a Coffee\">\u003C\u002Fa>\n   \n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsponsors\u002FDonchitos\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FGitHub%20Sponsors-ea4aaa?style=for-the-badge&logo=githubsponsors&logoColor=white\" alt=\"GitHub Sponsors\">\u003C\u002Fa>\n\u003C\u002Fp>\n\n- **[Buy Me a Coffee](https:\u002F\u002Fwww.buymeacoffee.com\u002Fdonchitos3)** — one-time support\n- **[GitHub Sponsors](https:\u002F\u002Fgithub.com\u002Fsponsors\u002FDonchitos)** — recurring support through GitHub\n\nSponsorships help fund time spent maintaining skills, adding new agents, keeping up with Claude Code and engine API changes, and responding to community issues.\n\n---\n\n*Built for Claude Code. Maintained and extended — contributions welcome via [GitHub Discussions](https:\u002F\u002Fgithub.com\u002FDonchitos\u002FClaude-Code-Game-Studios\u002Fdiscussions).*\n\n## License\n\nMIT License. See [LICENSE](LICENSE) for details.\n","Claude Code Game Studios 项目将单个 Claude Code 会话转变为一个完整的虚拟游戏开发工作室。该项目包含49个AI代理，具备73种工作流技能，并模仿真实游戏工作室的层级结构进行协调运作。其核心功能包括专业化的AI代理团队、明确的责任分工以及质量控制流程，确保从创意构思到最终发布整个过程中的项目组织性和一致性。适用于希望通过AI辅助进行独立或小型团队游戏开发的场景，支持Godot、Unity和Unreal Engine等主流游戏引擎。",2,"2026-06-11 03:51:06","high_star"]