The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Close the editor that's open for debug_helper.js; I need that space back to open the new log file…
Execute — do the immediate task
+Close the editor that's open for debug_helper.js; I need that space back to open the new log file before the stand-up.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I hand this workspace to QA, close editors that are irrelevant to the test scenario: close…
Improve — make it easier to accept
+Before I hand this workspace to QA, close editors that are irrelevant to the test scenario: close debug_helper.js and old_experiment.ipynb, leaving only the files the QA lead needs. Tell me which files will be closed and if any have unsaved work.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I just closed utils.py while trying to close a temporary scratch file and I'm not sure if I saved…
Decide — diagnose the stuck moment
+I accidentally closed the wrong file during a refactor
I just closed utils.py while trying to close a temporary scratch file and I'm not sure if I saved my edits. I can't find the undo history. Should I reopen from disk and reapply recent changes, or fess up to the reviewer and delay the PR? Which action minimizes risk of lost work and keeps trust?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+I keep accumulating dozens of open editors and lose track of what I changed. What habit can I adopt…
Become — change the pattern
+I habitually leave old editors open until the workspace is cluttered
I keep accumulating dozens of open editors and lose track of what I changed. What habit can I adopt to close irrelevant files regularly without risking lost edits? Recommend a simple routine or keystrokes I can use at the end of each coding session.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
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.