branch-review

Teach maths one concept at a time, checking each with a question.

Agree a spec for a piece of work and write its failing acceptance tests, ready for /build.

Build an approved spec with no conversation — make every check pass, run up to three review rounds, and write a summary the user audits afterwards.

After you have audited a finished task, find what the harness got wrong and propose at most one change to a skill or check so it does not happen again.

Communication style for the assistant — no follow-up nudges, one direct question when unsure, no hedging, no padding patterns, claims labelled with their…

Grill the user relentlessly about a plan, decision, or idea.

Do not paper over missing values with `??

Generic code style defaults — no comments, no single-character variables, braces on all if statements, blank lines between logical sections, prefer existing…

Test files live next to source — `foo.ts` → `foo.test.ts`, `Bar.tsx` → `Bar.test.tsx`.

Safe handling of stateful AWS resources in CDK — explicit removal policies, deletion protection, backup retention, snapshot-on-delete.

TypeScript discipline — trust the types, no defensive runtime checks for things the compiler already guarantees.

AWS CDK CustomResource patterns — Version property to force re-runs on behavior change, idempotent handlers, proper Create/Update/Delete handling.