Ship more without lowering the review bar

The steps, in order

1. 1

   Give the assistant your conventions

   A rules file with folder structure, testing approach and forbidden patterns.

   Use Cursor
2. 2

   Start from the test

   Acceptance criteria first means you can tell whether generated code is right.

   Task guide: Ship a feature in an existing codebase
3. 3

   Explain before you change

   Have unfamiliar code summarised, including who calls it, before editing.

   Use Claude
4. 4

   Keep diffs small

   One concern per commit. Large generated diffs are the main source of hidden bugs.
5. 5

   Review security by hand

   Auth, access rules and data queries never get accepted as generated.
6. 6

   Automate a recurring process

   Pick one repeated chore, turn it into an agent run with logging and alerts.

   Use n8nTask guide: Build an agent that does multi-step work