◆ JavaScript

Minify code for production

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to ship the minified bundle for Friday. Take the attached JavaScript file, remove…+
I need to ship the minified bundle for Friday. Take the attached JavaScript file, remove comments and whitespace, shorten variable names where safe, and output a single minified file that keeps source map references intact. Don’t change runtime behavior; check for any global name collisions first and warn me if there are any.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I hand this to QA, make the minified code easy to inspect when there’s a bug. Surface…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentStaging passed lint and unit tests, then the minified bundle started throwing undefined is not…+
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?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several releases we lose small runtime behaviors after minification—errors only in some…+
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?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.