Repro First
Use when fixing a reported bug — reproduce it with a failing test before touching the code, then make the minimal fix at the true cause; never patch the symptom or files unrelated to the bug.
Thrift
Use on every coding task to spend tokens and turns proportionally to the change: no redundant re-reads, no full-suite runs for trivial edits, batch related operations, verify once — without ever skipping verification the task actually needs.
Repo Cover
>
Underkill
Use when writing or modifying code — implementing features, refactoring, or fixing bugs — to prevent over-engineering: unrequested abstractions, options, config, dependencies, and defensive code. Build exactly what was asked, nothing more.
Tests That Bite
Use when writing tests — new suites or additions to existing ones — to make every test actually catch the bug it guards against: behavior-focused assertions, boundary coverage, no vacuous or implementation-coupled tests.