Multiline, Imports and Cross-File Portals

Done means Tab helps complete the surrounding edit while you verify the whole effect.

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

Use Tab when one local change implies imports, nearby edits or a matching edit in another file. 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. 1Make the first edit yourself so the model sees the pattern.
2. 2Accept multiline suggestions only after scanning all changed lines.
3. 3Follow portal jumps when Cursor predicts a related file needs the same change.
4. 4Run the smallest check that catches imports, types or broken references.

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.