What problem does it solve? Teams repeatedly re-fight settled battles: re-proposing rejected fixes, "fixing" deliberate design oddities, or re-opening decisions that already cost real time. This Skill provides a searchable incident chronicle so an agent checks history before changing anything that looks odd. ## Core Features & Use Cases - Incident chronicle with statuses: Every major investigation, dead end, and revert is recorded with root cause, evidence (SHA/journal), and a status of settled, fenced-off, or still-open. - Deliberate oddities table: Documents counterintuitive configurations (hmr:false, muted SFX engine, cook-anywhere) that must not be "fixed". - Doctrine index: Maps each incident to the standing rule it minted and its enforcement rung (hook, gate, norm, or philosophy). - Use Case: Before proposing to re-enable HMR in a Vite dev server, consult the chronicle to learn that hmr:false plus an inert /@vite/client is the only complete fix for reload-yanking a live game, with the exact commit SHAs cited. ## Quick Start Ask the agent to check the failure chronicle for whether this issue or design question has happened before, citing the relevant incident and rule.
