What problem does it solve? Debugging the kami-kakushi incremental RPG involves many recurring failure modes — red verify gates, dead dev servers, mass e2e failures from the wrong app on a port, phantom UI defects caused by test harnesses, and cross-file test leakage. This Skill provides a symptom-to-triage playbook and a measurement-tool catalog so you diagnose with evidence instead of guessing. ## Core Features & Use Cases - Symptom-to-triage tables: Maps concrete symptoms (verify gate RED, port 5264 in use, e2e mass-red, orphan-id save alarms, fixture drift, gen byte-compare failures) to first moves and follow-up recipes. - Discriminating experiments: Provides worktree-HEAD verification, attribution proofs for unexpected balance changes, control-verb tests, and shared-tree-safe git bisect procedures. - Measurement catalog: Documents the full window.__qa headless play API, scripted sensors (screenshot gallery, balance sim, pacing report, fixture checks), and human-side telemetry sensors. - Use Case: When e2e tests fail en masse with nonsense errors like "__qa.fixtures is not a function", follow the playbook to probe which app answers port 5265 before debugging your own code. ## Quick Start Load this skill whenever a verify gate fails, the dev server seems dead, e2e tests are red, or any UI behavior looks wrong, then follow the matching symptom row in the triage table.
