mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 04:51:46 +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>
39 lines
3.2 KiB
Markdown
39 lines
3.2 KiB
Markdown
# Available Skills (Slash Commands)
|
|
|
|
| Command | Purpose |
|
|
|---------|---------|
|
|
| `/design-review` | Review a game design document for completeness and consistency |
|
|
| `/code-review` | Architectural code review for a file or changeset |
|
|
| `/playtest-report` | Generate a structured playtest report template |
|
|
| `/balance-check` | Analyze game balance data and flag outliers |
|
|
| `/sprint-plan` | Generate or update a sprint plan |
|
|
| `/bug-report` | Create a structured bug report |
|
|
| `/architecture-decision` | Create an Architecture Decision Record (ADR) |
|
|
| `/asset-audit` | Audit assets for naming, sizing, and pipeline compliance |
|
|
| `/milestone-review` | Review milestone progress and generate status report |
|
|
| `/onboard` | Generate onboarding context for a new contributor or agent |
|
|
| `/prototype` | Scaffold a throwaway prototype to test a mechanic or technical approach |
|
|
| `/release-checklist` | Generate and validate a pre-release checklist for the current build |
|
|
| `/changelog` | Auto-generate changelog from git commits and sprint data |
|
|
| `/retrospective` | Run a structured sprint or milestone retrospective |
|
|
| `/estimate` | Produce a structured effort estimate with complexity and risk breakdown |
|
|
| `/hotfix` | Emergency fix workflow with audit trail, bypassing normal sprint process |
|
|
| `/tech-debt` | Scan, track, prioritize, and report on technical debt across the codebase |
|
|
| `/scope-check` | Analyze feature or sprint scope against original plan, flag scope creep |
|
|
| `/localize` | Localization workflow: scan for hardcoded strings, extract, validate translations |
|
|
| `/perf-profile` | Structured performance profiling with bottleneck identification and recommendations |
|
|
| `/project-stage-detect` | Automatically analyze project state, detect stage, identify gaps, and recommend next steps |
|
|
| `/reverse-document` | Generate design or architecture documents from existing implementation (works backwards from code) |
|
|
| `/team-combat` | Orchestrate combat team: game-designer + gameplay-programmer + ai-programmer + tech-artist + sound-designer + qa-tester |
|
|
| `/team-narrative` | Orchestrate narrative team: narrative-director + writer + world-builder + level-designer |
|
|
| `/team-ui` | Orchestrate UI team: ux-designer + ui-programmer + art-director |
|
|
| `/team-release` | Orchestrate release team: release-manager + qa-lead + devops-engineer + producer |
|
|
| `/team-polish` | Orchestrate polish team: performance-analyst + tech-artist + sound-designer + qa-tester |
|
|
| `/team-audio` | Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer |
|
|
| `/team-level` | Orchestrate level team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester |
|
|
| `/launch-checklist` | Complete launch readiness validation across all departments |
|
|
| `/patch-notes` | Generate player-facing patch notes from git history and internal data |
|
|
| `/brainstorm` | Guided ideation using professional studio methods (MDA, SDT, Bartle, verb-first) |
|
|
| `/gate-check` | Validate readiness to advance between development phases (PASS/CONCERNS/FAIL) |
|
|
| `/setup-engine` | Configure engine + version, detect knowledge gaps, populate version-aware reference docs |
|