Make One Small Change and Review the Diff

Done means one small edit lands with a diff you understand and can undo.

Fast edits still need a boundary: accept the useful completion, then review the patch.

Use Agent or inline edit when you have one low-risk change with a clear expected result. Keep the boundary narrow.

Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.

Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.

Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.

1. 1State the change, the files in scope and the behavior that must not change.
2. 2Choose inline edit for one selected region or Agent if the task crosses files.
3. 3Inspect the diff instead of trusting the summary.
4. 4Run the smallest relevant check and keep the evidence with your notes.

The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.

Verification decides the next move.

Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.