2 ready prompts
Written for the moment this actually comes up.
Improve — make it easier to accept
+Before I start debugging, make it easy for me to pick the right launch config: list Dev, Attach,…
Improve — make it easier to accept
+Before I start debugging, make it easy for me to pick the right launch config: list Dev, Attach, and Test and show the command and cwd each will run. Highlight whether source maps are enabled and whether the process will restart on file change. If Dev is missing source maps or has wrong cwd, suggest the precise change so stepping lands on my TypeScript sources. Ladder L2
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across several repos I waste time starting debug sessions that either attach to the wrong process,…
Become — change the pattern
+Debug sessions often fail to stop where I expect across projects.
Across several repos I waste time starting debug sessions that either attach to the wrong process, use wrong sourcemaps, or restart with a different build artifact. Where is the recurring mistake — my launch configs, build outputs, or the way I start processes — and what consistent changes to my workflow or repo config will make debug sessions reliably hit my breakpoints? 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.