The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need to run this notebook cell now. Focus on the current cell only: run it, wait for completion,…
Execute — do the immediate task
+I need to run this notebook cell now. Focus on the current cell only: run it, wait for completion, and if it errors, show me the full traceback in the output pane so I can copy it into the bug report.
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 execute, make it easy to spot side effects — surface the cell tags and any cell-level…
Improve — make it easier to accept
+Before I execute, make it easy to spot side effects — surface the cell tags and any cell-level environment variables, highlight long-running status, and show estimated runtime if available so a reviewer can decide whether to run it now.
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 ran a cell and it shows no output and the kernel status hasn’t changed. I’m not sure if the cell…
Decide — diagnose the stuck moment
+I hit run and the cell seemed to hang.
I ran a cell and it shows no output and the kernel status hasn’t changed. I’m not sure if the cell is genuinely executing, the kernel is busy elsewhere, or it deadlocked. What quick checks should I perform in order to determine which it is, and what’s the best immediate step to recover without losing recent state?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over multiple notebooks I keep running cells repeatedly or skipping ones that haven’t executed,…
Become — change the pattern
+I waste time re-running cells because I can’t tell which ones actually executed.
Over multiple notebooks I keep running cells repeatedly or skipping ones that haven’t executed, which breaks experiment reproducibility. What simple discipline or UI habit will save time and make runs reliable so I don’t accidentally overwrite results or miss a step?
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.