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/hooks-reference/pre-commit-design-check.md

@@ -0,0 +1,62 @@
+# Hook: pre-commit-design-check
+
+## Trigger
+
+Runs before any commit that modifies files in `design/` or `assets/data/`.
+
+## Purpose
+
+Ensures design documents and game data files maintain consistency and
+completeness before they enter version control. Catches missing sections,
+broken cross-references, and invalid data before they propagate.
+
+## Implementation
+
+```bash
+#!/bin/bash
+# Pre-commit hook: Design document and game data validation
+# Place in .git/hooks/pre-commit or configure via your hook manager
+
+DESIGN_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep -E '^design/')
+DATA_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep -E '^assets/data/')
+
+EXIT_CODE=0
+
+# Check design documents for required sections
+if [ -n "$DESIGN_FILES" ]; then
+    for file in $DESIGN_FILES; do
+        if [[ "$file" == *.md ]]; then
+            # Check for required sections in GDD documents
+            if [[ "$file" == design/gdd/* ]]; then
+                for section in "Overview" "Detailed" "Edge Cases" "Dependencies" "Acceptance Criteria"; do
+                    if ! grep -qi "$section" "$file"; then
+                        echo "ERROR: $file missing required section: $section"
+                        EXIT_CODE=1
+                    fi
+                done
+            fi
+        fi
+    done
+fi
+
+# Validate JSON data files
+if [ -n "$DATA_FILES" ]; then
+    for file in $DATA_FILES; do
+        if [[ "$file" == *.json ]]; then
+            if ! python -m json.tool "$file" > /dev/null 2>&1; then
+                echo "ERROR: $file is not valid JSON"
+                EXIT_CODE=1
+            fi
+        fi
+    done
+fi
+
+exit $EXIT_CODE
+```
+
+## Agent Integration
+
+When this hook fails, the committer should:
+1. For missing design sections: invoke the `game-designer` agent to complete
+   the document
+2. For invalid JSON: invoke the `tools-programmer` agent or fix manually