No767

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

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

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform.

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

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

Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind…

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session…

Index of the engineering principles. Load it whenever work is non-trivial: designing types or a signature, refactoring, debugging…

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes…

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

Fan out N parallel workers, drain them, and return one report.

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