Game Studio Agent Architecture — complete setup (Phases 1-7)

48 coordinated Claude Code subagents for indie game development:
- 3 leadership agents (creative-director, technical-director, producer)
- 10 department leads (game-designer, lead-programmer, art-director, etc.)
- 23 specialist agents (gameplay, engine, AI, networking, UI, tools, etc.)
- 12 engine-specific agents (Godot, Unity, Unreal with sub-specialists)

Infrastructure:
- 34 skills (slash commands) for workflows, reviews, and team orchestration
- 8 hooks for commit validation, asset checks, session management
- 11 path-scoped rules enforcing domain-specific standards
- 28 templates for design docs, reports, and collaborative protocols

Key features:
- User-driven collaboration protocol (Question → Options → Decision → Draft → Approval)
- Engine version awareness with knowledge-gap detection (Godot 4.6 pinned)
- Phase gate system for development milestone validation
- CLAUDE.md kept under 80 lines with extracted doc imports

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/docs/rules-reference.md

@@ -0,0 +1,17 @@
+# Path-Specific Rules
+
+Rules in `.claude/rules/` are automatically enforced when editing files in matching paths:
+
+| Rule File | Path Pattern | Enforces |
+| ---- | ---- | ---- |
+| `gameplay-code.md` | `src/gameplay/**` | Data-driven values, delta time, no UI references |
+| `engine-code.md` | `src/core/**` | Zero allocs in hot paths, thread safety, API stability |
+| `ai-code.md` | `src/ai/**` | Performance budgets, debuggability, data-driven params |
+| `network-code.md` | `src/networking/**` | Server-authoritative, versioned messages, security |
+| `ui-code.md` | `src/ui/**` | No game state ownership, localization-ready, accessibility |
+| `design-docs.md` | `design/gdd/**` | Required 8 sections, formula format, edge cases |
+| `narrative.md` | `design/narrative/**` | Lore consistency, character voice, canon levels |
+| `data-files.md` | `assets/data/**` | JSON validity, naming conventions, schema rules |
+| `test-standards.md` | `tests/**` | Test naming, coverage requirements, fixture patterns |
+| `prototype-code.md` | `prototypes/**` | Relaxed standards, README required, hypothesis documented |
+| `shader-code.md` | `assets/shaders/**` | Naming conventions, performance targets, cross-platform rules |