An open-source template that brings an entire game studio organization into a Claude Code session. It ships with 49 specialized agents and 73 slash commands (skills) covering the pipeline from planning and design through programming, art, audio, narrative, QA, and release. Instead of handing everything to a single general-purpose assistant, it splits roles across three tiers ─ directors, department leads, and specialist staff ─ so the granularity of each decision and its scope of responsibility stay clear. Built by Donchitos and released under the MIT license, it supports Godot 4, Unity, and Unreal Engine 5.
Key Features
-
A three-tier studio organization: Tier 1 holds the directors (creative director, technical director, producer), Tier 2 the department leads (game designer, lead programmer, art director, audio director, narrative director, QA lead, release manager, localization lead), and Tier 3 the specialists (gameplay, engine, AI, network, tools, and UI programmers, plus designers, artists, writers, and QA testers). Higher tiers are assigned stronger models ─ Opus for Tier 1, Sonnet and Haiku for the tiers below
-
73 slash commands: Every stage of the development pipeline, from concept work to implementation, testing, and release preparation, is predefined as a command. Running
/startbegins a guided onboarding, and an in-progress project can jump straight to the skill matching its current phase -
Support for the three major engines: Dedicated engine specialists are provided for Godot 4 (GDScript, shaders, GDExtension), Unity (DOTS/ECS, VFX, UI Toolkit), and Unreal Engine 5 (GAS, blueprints, replication)
-
Proposals always come with options, and the final call stays with you: The agents are designed to ask questions, present multiple options, and wait for approval rather than charging ahead on their own. Review strictness is adjustable, from “full” (all gates enabled) to “solo” (no gates)
-
12 automated validation hooks: Hooks run on commit, on asset additions, and at session start and end, checking for hardcoded values, naming convention violations, broken JSON, and gaps in design documents. This mechanically prevents ad-hoc implementation from piling up
-
Path-scoped coding standards and templates: The template includes 11 coding standards applied according to where a file lives, plus 41 document templates for design documents, technical specs, and planning
Pricing
| Item | Price | Notes |
|---|---|---|
| Claude Code Game Studios itself | Free (MIT license) | Clone from GitHub and use. Optional support via Buy Me a Coffee / GitHub Sponsors |
| Claude Code (prerequisite) | Purchased separately | Requires a paid Claude plan or pay-as-you-go Anthropic API usage |
Pricing reflects information as of August 2026. The template itself is entirely free and open source, but running it requires a working Claude Code environment. For the latest details, see the official repository and the Claude pricing page.
Pros & Cons
✅ Pros
- 49 game-development-focused agents are ready from the start, so there is no need to write agent definitions from scratch
- The three-tier split makes it clear which decisions belong to whom, reducing the chance of a review being skipped
- Validation hooks run automatically on commit, closing off the entry points for technical debt such as hardcoded values and inconsistent naming
- Covers Godot, Unity, and Unreal, offering support that goes into engine-specific conventions
- The MIT license means agents, skills, and rules can all be freely modified to match how your team works
⚠️ Cons
- It depends on Claude Code, so it does not run standalone and requires a separate Claude environment (a paid plan or equivalent)
- 49 agents and 73 commands are a lot to take in at first, and there is a learning curve before you know where to start
- It is primarily tested on Windows 10; macOS and Linux run through POSIX-compatible fallbacks. Desktop notifications are implemented for Windows (PowerShell) only and do nothing on other platforms
- For solo developers and small teams, the full approval gates can feel heavy (the “solo” mode lightens them, at the cost of fewer checks)
- It is open source published by an individual, so there is no support desk or update guarantee like a commercial product
Comparison with Similar Services
| Criteria | Claude Code Game Studios | wshobson/agents | Claude Code default (DIY) |
|---|---|---|---|
| Focus area | Game development | General software development | Any purpose |
| Number of agents | 49 (three tiers) | 76 (flat structure) | Only what you define |
| Bundled skills | 73 slash commands | Distributed as plugins | Build your own |
| Validation hooks | 12 included | None | Configure your own |
| Engine support | Godot / Unity / Unreal | None | None |
| License | MIT | Open source | ─ |
Who Is It For
- Anyone who wants to build a game with Claude Code but has watched a single assistant break down when handed the whole pipeline from planning to release
- Developers on Godot, Unity, or Unreal who want support grounded in engine-specific conventions
- Process-minded indie developers who want design documents and review structure even in solo work
- Small game studios that want clear role separation but do not have the headcount for it
- Claude Code users looking for a practical, real-world example to learn how agent definitions are written
Summary
Claude Code Game Studios takes the idea of treating AI agents as an organization with distinct roles ─ rather than one all-purpose assistant ─ and makes it concrete in the context of game development. With 49 agents, 73 skills, and 12 validation hooks already assembled, it removes the trial and error that normally comes before you can design agents of your own. On the other hand, the setup is large, and some features are limited outside Windows. A realistic approach is to clone it, run /start, get the full picture through the guided onboarding, and then trim the agents and rules down to fit your own project.