principle-experience-first

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away.

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it.

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which…

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".

Find the mistakes agents keep repeating in this repo and make each one impossible.

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it.

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks.

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase.