mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 13:01:50 +00:00
ad540fe75d
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>
16 lines
796 B
Markdown
16 lines
796 B
Markdown
---
|
|
paths:
|
|
- "design/gdd/**"
|
|
---
|
|
|
|
# Design Document Rules
|
|
|
|
- Every design document MUST contain these 8 sections: Overview, Player Fantasy, Detailed Rules, Formulas, Edge Cases, Dependencies, Tuning Knobs, Acceptance Criteria
|
|
- Formulas must include variable definitions, expected value ranges, and example calculations
|
|
- Edge cases must explicitly state what happens, not just "handle gracefully"
|
|
- Dependencies must be bidirectional — if system A depends on B, B's doc must mention A
|
|
- Tuning knobs must specify safe ranges and what gameplay aspect they affect
|
|
- Acceptance criteria must be testable — a QA tester must be able to verify pass/fail
|
|
- No hand-waving: "the system should feel good" is not a valid specification
|
|
- Balance values must link to their source formula or rationale
|