3 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+I need the editor showing the test file called test_api.py. Switch to the tab labeled test_api.py…
Execute — do the immediate task
+I need the editor showing the test file called test_api.py. Switch to the tab labeled test_api.py now so I can run the tests fast.
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 send this branch for review, reorder open tabs so the implementation file is next to its…
Improve — make it easier to accept
+Before I send this branch for review, reorder open tabs so the implementation file is next to its spec: move main.py next to main_spec.py and surface tests first. Flag any tabs with unsaved changes that will confuse the reviewer.
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 executed the wrong test because the open tab was the helper file, not the spec. I'm afraid I…
Decide — diagnose the stuck moment
+I clicked the wrong tab and ran tests on the wrong file
I just executed the wrong test because the open tab was the helper file, not the spec. I'm afraid I committed with the wrong focus. Should I switch to the spec tab and re-run, or abort and explain in the PR? Which keeps my credibility with the reviewer this afternoon?
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.