painhardcore

Apply when integrating a new requirement into an existing design.

Apply when concurrent actors might write to the same file, branch, key, or state object.

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).

Apply when sequencing an addition, refactor, or rewrite.

Fan out N independent workers, collect their results, and return one report for coverage, races, gauntlets, or exploration.

Explain a body of work plainly so a person actually understands it.

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language.

Cut AI tells from any writing. Must always apply.

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax.