2 ready prompts
Written for the moment this actually comes up.
Decide — diagnose the stuck moment
+I closed a terminal and the side bar unexpectedly stayed open; I'm worried the reviewer will get…
Decide — diagnose the stuck moment
+I just opened a presentation window and the file tree covers the code
I closed a terminal and the side bar unexpectedly stayed open; I'm worried the reviewer will get distracted by the file list. Should I hide the side bar now or leave it so they can open the files themselves? What is the least risky move for a one-on-one review in ten minutes?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every demo I give, participants get distracted by the file list and ask where things are. How do I…
Become — change the pattern
+I keep shipping with the file tree visible during demos
Every demo I give, participants get distracted by the file list and ask where things are. How do I change my habit so I start sessions with the side bar hidden and only reveal it when needed? Recommend a simple checklist or two short keystrokes to make it automatic.
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.