exhaust-inhalationDetect and repair personal circumstances or authoring discussion leaking into generated artifacts, including instructions, code, tests, commit messages and UI. Use when such a leak is spotted or suspected, or when translating conversational background into persistent output.
naming-is-hardApply naming and wording doctrine to code symbols, files, branches, docs, UI copy, and mixed Dutch/English terms.
programming-philosophyUse when planning, writing, refactoring, or reviewing software, especially reversible decisions, scope, command-query separation, root-cause fixes, DRY, and error handling.
scar-tissueUse when corrective work, migrations, living docs, or temporary diagnostic tests leave superseded residue, or before handoff.
testing-philosophyUse when writing tests, debugging failures, reviewing test strategy, or judging suite health.