Menu
Test-Driven Development combined with emergent playtesting for Quest Keeper AI. Use when running playtest sessions, writing tests, debugging game feel issues, or following the RED-GREEN-REFACTOR cycle.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Version control discipline for Quest Keeper AI development. Enforces the "commit early, commit often" pattern.
Frontend development skill for Quest Keeper AI Tauri application. Use when working on React components, Zustand stores, Three.js battlemaps, TailwindCSS styling, or Tauri shell integration. Triggers on mentions of frontend, React, Zustand, Three.js, battlemap, UI, viewport, or Tauri.
Master orchestration skill for Quest Keeper AI development. Use when working on ANY part of Quest Keeper AI - coordinates between frontend (Tauri/React), backend (rpg-mcp), and documentation. Triggers on any mention of Quest Keeper, rpg-mcp, game development for this project, or when referencing the Agents/ folder.
| name | tdd-playtest |
| description | Test-Driven Development combined with emergent playtesting for Quest Keeper AI. Use when running playtest sessions, writing tests, debugging game feel issues, or following the RED-GREEN-REFACTOR cycle. |
We are the player. Not a tester, not a developer. A player who wants to have fun.
1. PLAY Experience the game as a player
2. DISCOVER Find friction, confusion, missing features
3. DEFINE What SHOULD happen? (Player perspective)
4. RED Write test that fails
5. GREEN Write minimal code to pass
6. REFACTOR Clean up
7. PLAY AGAIN Does it feel right now?
Add to Agents/EMERGENT_DISCOVERY_LOG.md:
### [CATEGORY-###] Title
**Severity:** CRITICAL | HIGH | MEDIUM | LOW
**Player Experience:** What happened vs what should happen