What problem does it solve?
The Minigame feature spans database schemas, business services, encryption tokens, and builder UI, with several unlinked code locations that silently assume only the Jackpot type works. This Skill prevents developers from missing one of the four jackpot-only gates, breaking concurrency-safe prize draws, or misusing the public play token when editing or extending the minigame system.
Core Features & Use Cases
- Architecture Map: Locates every minigame concern, from Drizzle schema partials and prize-draw math to the public play page and jackpot preview components.
- Trap Documentation: Catalogs nine known pitfalls, including the four-place jackpot-only enforcement, SELECT FOR UPDATE concurrency patterns, and the intentional no-redistribution behavior when prizes sell out.
- Extension Recipe: Provides a step-by-step checklist for adding gameplay for a new minigame type (luckyWheel, gashapon, drawLots, scratchOff) without missing any gate.
- Use Case: When asked to enable the luckyWheel minigame type, follow the recipe to update the type picker, play action gate, public page gate, and preview dispatch, then run the listed vitest suites to verify.
Quick Start
Ask the agent to add gameplay support for the luckyWheel minigame type and verify the changes with the business and encryption test suites.