3 ready prompts
Written for the moment this actually comes up.
Improve — make it easier to accept
+Before I step through, make the debugging session easy to follow for Jake: highlight the current…
Improve — make it easier to accept
+Before I step through, make the debugging session easy to follow for Jake: highlight the current source file and line, show the local variables pane prominently, and keep breakpoints visible. If any inline source differs from disk, flag it. Stop stepping into third‑party library files unless a project file is involved. Ladder L2
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
+The program paused on the breakpoint inside handleUserRequest; the user id is undefined but I…
Decide — diagnose the stuck moment
+Program paused at a breakpoint but the value is unexpected
The program paused on the breakpoint inside handleUserRequest; the user id is undefined but I expected a string. I do not know whether the undefined came from earlier parsing or from this function’s argument wiring. Which is the most likely cause and what should I do next to confirm — add a breakpoint earlier at request parsing, inspect the call site, or log the caller’s value? Ladder L5
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 week I spend an hour stepping through stack frames to find where nulls originate. I keep…
Become — change the pattern
+I repeatedly waste time hunting a null/undefined through runs
Every week I spend an hour stepping through stack frames to find where nulls originate. I keep restarting, miss the caller’s context, and reintroduce the bug in later fixes. What habit will reduce this debugging churn — better preconditions, more unit tests around the parser, adding strategic breakpoints at call sites, or using watch expressions? Recommend the single most effective change and the quick discipline to adopt now. Ladder L6
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.