Game Review — Code Auditor

Prerequisites

• Apply relevant engineering and design skills based on the detected code domains (see Phase 0)

Phase 0 — Context Load (silent)

1. READ docs/mvp-first-draft.md if it exists (provides architectural intent for comparison)
2. READ docs/build-registry.md if it exists (tracks what's built vs mocked)
3. Determine scope from the user's message:
   • If a component name or path was provided: focus on src/[component]/ or the specified path
   • If nothing provided: review all of src/
4. Scan the target scope to identify which technology domains are present (auth, payments, WebSocket, Redis, BullMQ, quests, etc.)
5. Apply only the skills relevant to the detected domains:
   • Auth detected → Apply the betterauth-integration skill
   • Payments/Stripe detected → Apply the stripe-game-payments skill