game-dev

# Game Development Five modes: **Design** (diagnosis, auditing, improvement), **Pipeline** (full lifecycle orchestration), **Sprite** (AI sprite generation), **Phaser** (2D engine builds), **GM** (large multi-system implementations). Cross-cutting concerns (audio, QA, deploy) load as needed. Classify the request and follow the matching section. ## Mode Selection | Mode | Signals | |------|---------| | **Design** | game design, improve game, retention, churn, core loop, audit, game feel, balance, economy | | **Pipeline** | make game, scaffold, game lifecycle, game audio, deploy game, game QA | | **Sprite** | AI sprite, generate character, portrait, spritesheet, animated sheet, pixel art | | **Phaser** | Phaser, 2D game, platformer, arcade physics, tilemap, side scroller | | **GM** | large GM implementation, multi-system GM, CPU systems, multi-wave overhaul | If the request spans modes, load both primary references. Design + Pipeline is common (design an improvement then implement it). Sprite + Phaser is common (generate assets then wire into a Phaser game). --- ## Design Mode Evidence-led game design diagnosis with 61 runnable capabilities. Start from repository evidence; never guess when the repo can answer. ### Workflow 1. **Intake.** Read target repository's governing files. Search for game, product, UI, analytics, and research guidance. Use file search to find design docs, player copy, rules, UI, config, tests, analytics, issues. Separate facts into: observed, doc...