donchitos

Find balance outliers, broken progressions, degenerate strategies, economy imbalances in formulas and data. 'Check game balance'.

Structured playtest report template, or turn existing playtest notes into structured feedback.

Guides the user through finding and choosing a game concept. Use when the user wants game ideas, a new concept, a game jam idea, or to explore other directions, including dropping the current idea and starting over.

Author the Art Bible — visual identity gating asset production. Run before /map-systems.

Orchestrate the narrative team — narrative-director, writer, world-builder, level-designer — for story, world lore, narrative-driven levels.

Reviews one design document for completeness, internal consistency, implementability, and design standards. Before handing to programmers.

Section-by-section GDD authoring for one system — walks through each required section, cross-references dependencies.

Decompose a concept into individual systems, map dependencies, prioritize design order, create the systems index.

Estimate task effort from complexity, dependencies, velocity, risk. Structured estimate with confidence levels.

Validate a UX spec, HUD design or pattern library — accessibility, GDD alignment, readiness. APPROVED / NOT ASSESSED / NEEDS REVISION / MAJOR REVISION NEEDED.

Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.

Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.

Scope creep check — current scope versus the original plan. Flags additions, quantifies bloat, recommends cuts. 'Any scope creep?'

Orchestrate the UI team through the UX pipeline — authoring, visual design, implementation, review, polish. Uses /ux-design, /ux-review, studio templates.

Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.

Guides a first-time user through onboarding and picks the right workflow. Use when the user is new, just cloned or installed the studio, has no idea or engine yet, asks where to begin, or wants to bring in an existing game.

Concept prototype before GDDs — throwaway HTML, Engine or Paper build, PROCEED/PIVOT/KILL/NOT ASSESSED. After /brainstorm and /setup-engine.

Configure engine and version. Pins it in CLAUDE.md; WebSearch fills reference docs when the version is beyond LLM training data.