Delete a file

Delete a file 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 the stray legacy file deleted before it breaks the build. Remove src/utils/oldParser.js from…
I need the stray legacy file deleted before it breaks the build. Remove src/utils/oldParser.js from the repository, then run the project’s test suite and tell me which tests fail within five minutes so I can revert if necessary.

Decide — diagnose the stuck moment

+
I deleted src/utils/oldParser.js because it looked unused, but the CI now fails with…

I just tried to run tests and they failed referencing the deleted module

I deleted src/utils/oldParser.js because it looked unused, but the CI now fails with ModuleNotFoundError and I can’t tell which runtime import triggers it. The build log references a transpiled path and there’s a legacy import in a vendor file. What’s the most likely cause and the fastest safe rollback or fix so CI green returns?

Become — change the pattern

+
Over the last year I’ve twice removed files that seemed unused and both times CI or production…

We keep deleting files that unexpectedly break things

Over the last year I’ve twice removed files that seemed unused and both times CI or production broke. I want a habit that prevents this without slowing routine cleanup. Where am I losing context and what concrete change to my PR checklist or branch testing would stop these regressions most reliably?

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.