2 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+I want to compare this implementation with the spec. Split the editor so I have main.js on the left…
Execute — do the immediate task
+I want to compare this implementation with the spec. Split the editor so I have main.js on the left and spec.md on the right, side by side for a quick review.
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 attempted a split to compare two versions and the editor kept swapping tabs instead of opening…
Decide — diagnose the stuck moment
+I just tried to view two files together and the editor replaced one with the other
I attempted a split to compare two versions and the editor kept swapping tabs instead of opening them side by side. I'm not sure if I used the right command. Should I try the split again or explain to the reviewer and continue sequentially? Which will be faster and least confusing for the demo?
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.