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/skills/team-polish/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: team-polish
+description: "Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality."
+argument-hint: "[feature or area to polish]"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task
+---
+When this skill is invoked, orchestrate the polish team through a structured pipeline.
+
+## Team Composition
+- **performance-analyst** — Profiling, optimization, memory analysis, frame budget
+- **technical-artist** — VFX polish, shader optimization, visual quality
+- **sound-designer** — Audio polish, mixing, ambient layers, feedback sounds
+- **qa-tester** — Edge case testing, regression testing, soak testing
+
+## How to Delegate
+
+Use the Task tool to spawn each team member as a subagent:
+- `subagent_type: performance-analyst` — Profiling, optimization, memory analysis
+- `subagent_type: technical-artist` — VFX polish, shader optimization, visual quality
+- `subagent_type: sound-designer` — Audio polish, mixing, ambient layers
+- `subagent_type: qa-tester` — Edge case testing, regression testing, soak testing
+
+Always provide full context in each agent's prompt (target feature/area, performance budgets, known issues). Launch independent agents in parallel where the pipeline allows it (e.g., Phases 3 and 4 can run simultaneously).
+
+## Pipeline
+
+### Phase 1: Assessment
+Delegate to **performance-analyst**:
+- Profile the target feature/area using `/perf-profile`
+- Identify performance bottlenecks and frame budget violations
+- Measure memory usage and check for leaks
+- Benchmark against target hardware specs
+- Output: performance report with prioritized optimization list
+
+### Phase 2: Optimization
+Delegate to **performance-analyst** (with relevant programmers as needed):
+- Fix performance hotspots identified in Phase 1
+- Optimize draw calls, reduce overdraw
+- Fix memory leaks and reduce allocation pressure
+- Verify optimizations don't change gameplay behavior
+- Output: optimized code with before/after metrics
+
+### Phase 3: Visual Polish (parallel with Phase 2)
+Delegate to **technical-artist**:
+- Review VFX for quality and consistency with art bible
+- Optimize particle systems and shader effects
+- Add screen shake, camera effects, and visual juice where appropriate
+- Ensure effects degrade gracefully on lower settings
+- Output: polished visual effects
+
+### Phase 4: Audio Polish (parallel with Phase 2)
+Delegate to **sound-designer**:
+- Review audio events for completeness (are any actions missing sound feedback?)
+- Check audio mix levels — nothing too loud or too quiet relative to the mix
+- Add ambient audio layers for atmosphere
+- Verify audio plays correctly with spatial positioning
+- Output: audio polish list and mixing notes
+
+### Phase 5: Hardening
+Delegate to **qa-tester**:
+- Test all edge cases: boundary conditions, rapid inputs, unusual sequences
+- Soak test: run the feature for extended periods checking for degradation
+- Stress test: maximum entities, worst-case scenarios
+- Regression test: verify polish changes haven't broken existing functionality
+- Test on minimum spec hardware (if available)
+- Output: test results with any remaining issues
+
+### Phase 6: Sign-off
+- Collect results from all team members
+- Compare performance metrics against budgets
+- Report: READY FOR RELEASE / NEEDS MORE WORK
+- List any remaining issues with severity and recommendations
+
+## Output
+A summary report covering: performance before/after metrics, visual polish changes, audio polish changes, test results, and release readiness assessment.