game-dev

Comprehensive game MVP interviewer and planner. Interviews you in progressive groups, researches genre conventions and reference games, then produces an actionable MVP First Draft with starter project files.

Execute in this exact order:

Builds a game component from the MVP plan — production TypeScript + Vitest tests + mock dependencies + build registry tracking. Run /game-architect first to generate the plan.

Adds a new feature to an existing MVP plan — scoped architect interview, scope validation against original plan, and integration into the build sequence. Run /game-architect first.

Adds or updates a single world lore entry (faction, location, NPC, or event) — validates against existing lore for consistency, applies the right template, and updates docs/world-lore.md.

Use for game design work — core loops, economy balance, level design, progression systems, UX flows, feature specs. Triggers on: design, balance, economy, progression, player experience, core loop, level design, UI flow, game feel, monetization, retention.

Use for implementing server-side game systems — schemas, API routes, WebSocket handlers, job queues, Redis patterns, auth, and payments. Triggers on: implement, add endpoint, create schema, set up queue, write migration, add WebSocket, fix bug, server-side, backend.

Use for all narrative content — quests, characters, NPCs, world lore, story arcs, factions, dialogue. Triggers on: create quest, add character, write NPC, world lore, story arc, faction, dialogue, narrative, coherence check.

Use when designing core game loops, feedback systems, player motivation models, MDA framework analysis, progression curves, difficulty tuning, reward schedules, or any genre-agnostic game design theory.

Use when designing virtual economies, currencies, sink/faucet balance, loot tables, crafting systems, shops, or inflation control. Triggers: economy, currency, sinks, loot, inflation, crafting, shop.

Use when designing game levels, environments, difficulty curves, pacing, encounter placement, or spatial layouts for any game genre. Triggers: level, pacing, difficulty curve, encounter, environment, spatial design.

Use when implementing procedural content generation, dungeon or map generation, procedural loot tables, world seeds, noise-based terrain, NPC behavior variation, or wave function collapse. Triggers: procedural, dungeon gen, map gen, loot table, world seed, noise, BSP, wave function collapse, randomization.

Use when designing quests, missions, objectives, quest trees, or reward structures. Requires quest-narrative-coherence check before any quest creation. Triggers: quest, mission, objectives, quest tree, rewards.

6 hooks across 5 events