Game Build — Component Builder

Prerequisites

• Requires docs/mvp-first-draft.md in the project (run game-architect first)

Phase 0 — Context Load (silent, mandatory before writing a single line of code)

Execute in this exact order:

1. Check if docs/mvp-first-draft.md exists in the project
   • If it does NOT exist: output ⛔ Cannot proceed. Run the game-architect skill first to generate the MVP plan. game-build requires an existing plan to avoid architectural drift. and stop.
2. READ docs/mvp-first-draft.md (the MVP plan from game-architect)
   • Check Section 10 (Out of Scope / Deferred): if the component name from the user's message matches any deferred item, output ⚠️ [component] was explicitly deferred: "[reason]". Building now may increase scope. Continue? and wait for confirmation before proceeding.
3. IDENTIFY which skills are relevant to the component name from the user's message — apply only those skills from: game-backend-architecture, game-design-fundamentals, quest-narrative-coherence, postgres-game-schema, redis-game-patterns, bullmq-game-queues, betterauth-integration, stripe-game-payments, elevenlabs-sound-music, game-state-sync, matchmaking-system, gameplay-analytics
4. READ docs/build-registry.md if it exists (create it if not, using the template below)
5. READ docs/world-lore.md if component touches narrative/quests