Copy, fill in, use

Stops the assistant from jumping straight into code.

I want to add [feature]. Before writing any code:
1. Ask me up to 5 questions if anything is missing.
2. List the files you will touch.
3. Write a step-by-step plan and how each step will be tested.
Don't start coding until I say "approved".

For a no-mercy review of a PR or a file.

Review the code below like a senior [language] developer.
Rank issues by severity: bugs, security, performance, readability.
For each issue: the line, why it's a problem, the fixed code.
If there are no issues, don't invent any. Say "no issues found".

[code]

Makes it work from evidence, not guesses.

I'm getting this error: [error message]
Expected: [what should happen]. Actual: [what happens].
First list 3 likely causes and how I can verify each one.
Then suggest the smallest fix for whichever one is confirmed.

For a red-green workflow.

For [function/feature], first write failing tests:
the normal case, edge values, invalid input.
Run the tests and show that they fail.
Then write the least code that makes them pass. Don't change the tests.