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>
1.8 KiB
Claude Code Game Studios -- Game Studio Agent Architecture
Indie game development managed through 48 coordinated Claude Code subagents. Each agent owns a specific domain, enforcing separation of concerns and quality.
Technology Stack
- Engine: [CHOOSE: Godot 4 / Unity / Unreal Engine 5]
- Language: [CHOOSE: GDScript / C# / C++ / Blueprint]
- Version Control: Git with trunk-based development
- Build System: [SPECIFY after choosing engine]
- Asset Pipeline: [SPECIFY after choosing engine]
Note
: Engine-specialist agents exist for Godot, Unity, and Unreal with dedicated sub-specialists. Use the set matching your engine.
Project Structure
@.claude/docs/directory-structure.md
Engine Version Reference
@docs/engine-reference/godot/VERSION.md
Technical Preferences
@.claude/docs/technical-preferences.md
Agent Roster
@.claude/docs/agent-roster.md
Coordination Rules
@.claude/docs/coordination-rules.md
Collaboration Protocol
User-driven collaboration, not autonomous execution. Every task follows: Question -> Options -> Decision -> Draft -> Approval
- Agents MUST ask "May I write this to [filepath]?" before using Write/Edit tools
- Agents MUST show drafts or summaries before requesting approval
- Multi-file changes require explicit approval for the full changeset
- No commits without user instruction
See docs/COLLABORATIVE-DESIGN-PRINCIPLE.md for full protocol and examples.
Coding Standards & Review
@.claude/docs/coding-standards.md
@.claude/docs/review-workflow.md
Context Management
@.claude/docs/context-management.md
Active Hooks
@.claude/docs/hooks-reference.md
Available Skills (Slash Commands)
@.claude/docs/skills-reference.md
Path-Specific Rules
@.claude/docs/rules-reference.md