Use multi-cursor editing

Use multi-cursor editing in Visual Studio Code — with three ready prompts, from the immediate task to the lasting pattern.

3prompt heights
Open it in the interactive atlas →

3 ready prompts

Written for the moment this actually comes up.

Execute — do the immediate task

+
I need to edit three places at once: update the error message in api/handlers/user.js, change the…
I need to edit three places at once: update the error message in api/handlers/user.js, change the variable name in lib/auth/tokens.js, and add a log line in scripts/migrate.js. Put cursors at the same logical spots and apply the three edits simultaneously so they share the same phrasing.

Improve — make it easier to accept

+
Before I run the multi-edit, make it simple for reviewers: show where similar error messages exist,…
Before I run the multi-edit, make it simple for reviewers: show where similar error messages exist, surface whether the variable tokenCount is used in arithmetic elsewhere, and flag any migrated scripts that expect the old log format so I can avoid breaking downstream parsing.

Become — change the pattern

+
I repeatedly use simultaneous cursors to rush through edits and end up with inconsistent naming or…

I keep misusing multi-cursor edits and introduce inconsistent variable names

I repeatedly use simultaneous cursors to rush through edits and end up with inconsistent naming or missed edge cases. Where am I losing credibility or time, and what practice would stop a bad bulk edit habit? Recommend one rule for when to use multi-cursor and one quick verification step to include in every PR.

Next to this one

Other code editor work people do in Visual Studio Code.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.