3 ready prompts
Written for the moment this actually comes up.
Improve — make it easier to accept
+Before I hand this to QA, make the minified code easy to inspect when there’s a bug. Surface the…
Improve — make it easier to accept
+Before I hand this to QA, make the minified code easy to inspect when there’s a bug. Surface the original function and variable names in an accompanying source map, keep meaningful names for exported APIs, and flag any transformations that might obscure stack traces. Also point out any code that a standard minifier would mangle but that I should preserve for diagnostics.
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
+Staging passed lint and unit tests, then the minified bundle started throwing undefined is not a…
Decide — diagnose the stuck moment
+The staging build crashed with odd undefineds after minification
Staging passed lint and unit tests, then the minified bundle started throwing undefined is not a function at runtime only in Safari. I’m worried a variable got renamed or a global was broken. I can’t reproduce locally with dev builds. What’s the most likely cause and the minimal next steps I should take to confirm and fix it without reverting the whole pipeline?
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 releases we lose small runtime behaviors after minification—errors only in some…
Become — change the pattern
+Minify step keeps introducing production bugs
Across several releases we lose small runtime behaviors after minification—errors only in some browsers or when scripts load in a different order. I’m wasting hours bisecting builds. What habit or build change will reduce these regressions and save me time while keeping bundles small?
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 programming language work people do in JavaScript.
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.