mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
Release 1.1.0 — one config file, and a process weight you choose
`project.yaml` at the repo root is now the single source of truth for a project's configuration, replacing `production/stage.txt`, `production/review-mode.txt` and `.claude/docs/technical-preferences.md` (all three still read as a fallback; nothing is force-deleted). **`modes.rigor` — one question instead of six.** `minimal`, `standard` or `full` fronts six knobs: `modes.workflow`, `docs.density`, `qa.level`, `modes.story_granularity`, `modes.review_mode` and `team.size`. It defaults to `minimal`, which is a change from 1.0's behaviour: the heavier tier was measured costing several times more to reach working code without producing a better result, and returning nothing when a fresh developer inherited the project. Pin `modes.rigor: standard` to keep 1.0's process level. Also in this release: - `/settings` to view or change any setting, and `project.local.yaml` for per-developer preferences that should not be committed. - `system_overrides` to hold one system to a higher standard than the rest of the project, and `testing.strict` to set per test type whether missing evidence blocks a story or warns. - A story that changes anything the player sees is not closed until the game has been launched, observed, and a screenshot retained in `production/qa/evidence/`. A parse check is not a run. This holds at every rigor level, including `minimal`, where automated tests are waived but the look is not. - The code root is engine-specific and enforced as such: Godot `src/`, Unity `Assets/`, Unreal `Source/<Module>/`. Two of the three will not build a project laid out any other way. - Migration tooling for existing projects: `.claude/scripts/migrate-v1-config.sh` converts a 1.0 layout, non-destructively by default, with a report to review before `--finalize` deletes anything. - Ask-before-write holds regardless of personal automation settings. Upgrading from 1.0 or earlier: see UPGRADING.md. Full list of changes: CHANGELOG.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016xvzG3i7pWQg4LjyDwWMXd
This commit is contained in:
Donchitos
co-authored by
Claude Opus 5
Claude Opus 5
parent
984023ddac
commit
d05699707f
@@ -3,16 +3,16 @@
|
||||
<p align="center">
|
||||
Turn a single Claude Code session into a full game development studio.
|
||||
<br />
|
||||
49 agents. 73 skills. One coordinated AI team.
|
||||
49 agents. 74 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/skills"><img src="https://img.shields.io/badge/skills-74-green" alt="74 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=".claude/rules"><img src="https://img.shields.io/badge/rules-13-red" alt="13 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>
|
||||
@@ -35,7 +35,9 @@ The result: you still make every decision, but now you have a team that asks the
|
||||
- [What's Included](#whats-included)
|
||||
- [Studio Hierarchy](#studio-hierarchy)
|
||||
- [Slash Commands](#slash-commands)
|
||||
- [Does it produce games, or documents?](#does-it-produce-games-or-documents)
|
||||
- [Getting Started](#getting-started)
|
||||
- [Configuration](#configuration)
|
||||
- [Upgrading](#upgrading)
|
||||
- [Project Structure](#project-structure)
|
||||
- [How It Works](#how-it-works)
|
||||
@@ -53,25 +55,25 @@ The result: you still make every decision, but now you have a team that asks the
|
||||
| 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.) |
|
||||
| **Skills** | 74 | 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 |
|
||||
| **Rules** | 13 | 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)
|
||||
Tier 1 — Directors
|
||||
creative-director technical-director producer
|
||||
|
||||
Tier 2 — Department Leads (Sonnet)
|
||||
Tier 2 — Department Leads
|
||||
game-designer lead-programmer art-director
|
||||
audio-director narrative-director qa-lead
|
||||
release-manager localization-lead
|
||||
|
||||
Tier 3 — Specialists (Sonnet/Haiku)
|
||||
Tier 3 — Specialists
|
||||
gameplay-programmer engine-programmer ai-programmer
|
||||
network-programmer tools-programmer ui-programmer
|
||||
systems-designer level-designer economy-designer
|
||||
@@ -82,6 +84,11 @@ Tier 3 — Specialists (Sonnet/Haiku)
|
||||
live-ops-designer community-manager
|
||||
```
|
||||
|
||||
Each agent declares a model in its frontmatter: the three directors ask for
|
||||
Opus, sixteen specialists name Sonnet or Haiku, and the remaining thirty
|
||||
**inherit your session's model**. Treat the tiers as seniority of role, not as
|
||||
a billing plan — most of the studio runs on whatever model you are already using.
|
||||
|
||||
### Engine Specialists
|
||||
|
||||
The template includes agent sets for all three major engines. Use the set that matches your project:
|
||||
@@ -94,10 +101,10 @@ The template includes agent sets for all three major engines. Use the set that m
|
||||
|
||||
## Slash Commands
|
||||
|
||||
Type `/` in Claude Code to access all 73 skills:
|
||||
Type `/` in Claude Code to access all 74 skills:
|
||||
|
||||
**Onboarding & Navigation**
|
||||
`/start` `/help` `/project-stage-detect` `/setup-engine` `/adopt`
|
||||
`/start` `/help` `/project-stage-detect` `/setup-engine` `/adopt` `/settings`
|
||||
|
||||
**Game Design**
|
||||
`/brainstorm` `/map-systems` `/design-system` `/quick-design` `/review-all-gdds` `/propagate-design-change`
|
||||
@@ -127,11 +134,40 @@ Type `/` in Claude Code to access all 73 skills:
|
||||
`/release-checklist` `/launch-checklist` `/changelog` `/patch-notes` `/hotfix` `/day-one-patch`
|
||||
|
||||
**Creative & Content**
|
||||
`/prototype` `/onboard` `/localize`
|
||||
`/prototype` `/vertical-slice` `/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`
|
||||
|
||||
## Does it produce games, or documents?
|
||||
|
||||
A fair question, and the answer is a measurement rather than a sample project.
|
||||
Four games were built from one brief at different `modes.rigor` levels and the
|
||||
documents each wrote **before its first line of game code** were counted:
|
||||
|
||||
| `modes.rigor` | Docs before first line of game code | Time |
|
||||
|---|---:|---:|
|
||||
| `minimal` | **1** (the one-page brief) | 0 min |
|
||||
| `standard` | 30 | 58 min |
|
||||
|
||||
All of them produced a running, tested game. Two blind reviewers and a human
|
||||
playtest then ranked the `standard` build **last** — the extra 29 documents
|
||||
bought traceability, not a better game.
|
||||
|
||||
### It runs the game and looks at it
|
||||
|
||||
The measurement above is about cost. The other half is whether the thing works,
|
||||
and for a game that means someone has to *look* at it — a passing test says
|
||||
nothing about a menu drawn off-screen. So a story that changes anything the
|
||||
player sees is not closed until the game has been launched, observed, and a
|
||||
screenshot retained in `production/qa/evidence/`. A parse check is not a run.
|
||||
This holds at every rigor level, including `minimal`, where automated tests are
|
||||
waived but the look is not.
|
||||
|
||||
The games themselves are deliberately **not** shipped here: this is a template
|
||||
you clone to start your own project, and somebody else's game in your repo is
|
||||
clutter, not evidence.
|
||||
|
||||
## Getting Started
|
||||
|
||||
### Prerequisites
|
||||
@@ -163,6 +199,54 @@ All hooks fail gracefully if optional tools are missing — nothing breaks, you
|
||||
- `/setup-engine godot 4.6` — configure your engine if you already know
|
||||
- `/project-stage-detect` — analyze an existing project
|
||||
|
||||
## Configuration
|
||||
|
||||
`project.yaml` at the repo root is the single source of truth for how the
|
||||
studio behaves on your project — engine, naming conventions, and a `modes`
|
||||
block that controls how much process every skill enforces. `/start` writes it
|
||||
for you; you rarely need to hand-edit it.
|
||||
|
||||
The one question that matters most is **`modes.rigor`** — `minimal`, `standard`,
|
||||
or `full`. It's a single front door over six separate knobs (`workflow` —
|
||||
which GDD sections are required, `docs.density`, `qa.level`,
|
||||
`story_granularity`, `review_mode` — how many director agents review your work,
|
||||
and `team.size`), so `/start` asks it once instead of six times:
|
||||
|
||||
- **`minimal`** (default) — jam-game speed. No GDDs required, terse docs, minimal QA evidence, solo review. `/start` → `/setup-engine` → `/dev-story` in a handful of steps.
|
||||
- **`standard`** — 5 required GDD sections, balanced doc depth, standard QA evidence, lean review.
|
||||
- **`full`** — all 8 GDD sections, thorough docs, full QA evidence on every story type, full director review.
|
||||
|
||||
`minimal` is the default because it was measured against the alternatives: the
|
||||
heavier tier cost several times more to reach working code, was ranked last on
|
||||
play quality, and returned nothing measurable when a fresh developer inherited
|
||||
the project. Raise it in one `/settings` call when your project grows — `/help`
|
||||
and `/gate-check` will suggest it when they see the signs.
|
||||
|
||||
Two escape hatches keep one setting from being a blunt instrument.
|
||||
**`system_overrides`** holds a single system to a higher standard than the rest
|
||||
of the project — your combat system gets the full treatment while everything
|
||||
else stays light. **`testing.strict`** sets, per test type (logic, integration,
|
||||
visual, UI, config), whether missing evidence blocks a story or merely warns.
|
||||
|
||||
Any of the six underlying knobs can still be set individually if you want a mix
|
||||
(e.g. `workflow: full` with `docs.density: terse` — comprehensive but compact).
|
||||
Two of them — `review_mode` (`full` / `lean` / `solo`) and `team.size` — are
|
||||
also **personal**: rigor sets the team-wide default, but you can override them
|
||||
per-developer in a gitignored `project.local.yaml` without touching the shared
|
||||
config. `modes.automation` (how often the AI pauses to ask before it acts) sits
|
||||
outside rigor and is likewise personally overridable.
|
||||
|
||||
View or change any setting with the `/settings` skill:
|
||||
|
||||
```
|
||||
/settings # view effective config
|
||||
/settings modes.review_mode # view one setting
|
||||
/settings modes.rigor=full # write to project.yaml (team-wide)
|
||||
/settings --local modes.review_mode=solo # write to project.local.yaml (just you)
|
||||
```
|
||||
|
||||
Full schema and per-setting behavior: `.claude/docs/effects-map.md`.
|
||||
|
||||
## Upgrading
|
||||
|
||||
Already using an older version of this template? See [UPGRADING.md](UPGRADING.md)
|
||||
@@ -176,14 +260,17 @@ 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
|
||||
skills/ # 74 slash commands (subdirectory per skill)
|
||||
hooks/ # 14 scripts (bash) — 12 event hooks, yaml-helper.sh,
|
||||
# and one opt-in diagnostic you wire yourself
|
||||
rules/ # 13 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
|
||||
templates/ # 39 document templates (+ per-section guidance)
|
||||
src/ # Game source code (Godot). The code root is
|
||||
# ENGINE-SPECIFIC: Unity compiles only
|
||||
# Assets/, Unreal builds from Source/<Module>/
|
||||
assets/ # Art, audio, VFX, shaders, data files
|
||||
design/ # GDDs, narrative docs, level designs
|
||||
docs/ # Technical documentation and ADRs
|
||||
@@ -191,8 +278,26 @@ tests/ # Test suites (unit, integration, performanc
|
||||
tools/ # Build and pipeline tools
|
||||
prototypes/ # Throwaway prototypes (isolated from src/)
|
||||
production/ # Sprint plans, milestones, release tracking
|
||||
CCGS Skill Testing Framework/ # QA for the skills and agents themselves — see below
|
||||
```
|
||||
|
||||
### Testing your customizations
|
||||
|
||||
CCGS is a template you are meant to edit. `CCGS Skill Testing Framework/` is how
|
||||
you check that an edited or newly written skill still holds up — a catalog of all
|
||||
74 skills and 49 agents, per-category quality rubrics, behavioral specs, and
|
||||
templates for writing specs of your own.
|
||||
|
||||
```
|
||||
/skill-test static [name] # structural linter — 7 compliance checks
|
||||
/skill-test category [name] # category-specific quality rubric
|
||||
/skill-test spec [name] # behavioral spec assertions
|
||||
/skill-test audit # coverage report across skills and agents
|
||||
/skill-improve [name] # test-fix-retest loop; keeps or reverts on score change
|
||||
```
|
||||
|
||||
It tests the *framework*, never your game — game tests live in `tests/`.
|
||||
|
||||
## How It Works
|
||||
|
||||
### Agent Coordination
|
||||
@@ -242,7 +347,10 @@ You stay in control. The agents provide structure and expertise, not autonomy.
|
||||
|
||||
### Path-Scoped Rules
|
||||
|
||||
Coding standards are automatically enforced based on file location:
|
||||
Coding standards are automatically enforced based on file location. The paths
|
||||
below show the Godot code root; on Unity read `src/` as `Assets/`, and on
|
||||
Unreal as `Source/<Module>/` — the engine's toolchain fixes that choice, and
|
||||
`/setup-engine` resolves it for you.
|
||||
|
||||
| Path | Enforces |
|
||||
|------|----------|
|
||||
@@ -251,7 +359,10 @@ Coding standards are automatically enforced based on file location:
|
||||
| `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 |
|
||||
| `design/gdd/**` | Required sections per `modes.workflow`, formula format, edge cases |
|
||||
| `design/narrative/**` | Lore consistency, character voice, canon levels |
|
||||
| `assets/data/**` | JSON validity, naming conventions, schema rules |
|
||||
| `assets/shaders/**` | Naming conventions, performance targets, cross-platform rules |
|
||||
| `tests/**` | Test naming, coverage requirements, fixture patterns |
|
||||
| `prototypes/**` | Relaxed standards, README required, hypothesis documented |
|
||||
|
||||
@@ -275,7 +386,7 @@ This is a **template**, not a locked framework. Everything is meant to be custom
|
||||
- **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.
|
||||
- **Tune process weight** — `modes.rigor` and its underlying knobs in `project.yaml` (see [Configuration](#configuration)). Override per-run with `--review solo` on any skill.
|
||||
|
||||
## Platform Support
|
||||
|
||||
|
||||
Reference in New Issue
Block a user