Adversarially harden code changes, plans, migrations, designs, and implementations before shipping. Use when the user asks to check mistakes, edge cases, second-order effects, risks, regressions, tests, performance bottlenecks, algorithmic complexity, or production failure modes. Also use for prompts like "harden this", "review before merge", "check the plan", "find what will break", or "improve if needed". Do not use for casual explanations or purely cosmetic rewrites.
2026-05-21