◆ JavaScript

Import a module

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskImport the date utilities from the shared library at src/lib/date-utils.js and use the…+
Import the date utilities from the shared library at src/lib/date-utils.js and use the formatIso function in this module. Add the import statement at the top and replace the existing inline formatter with a call to formatIso(date).
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 open the pull request, make the import and usage review-friendly: show the exact…+
Before I open the pull request, make the import and usage review-friendly: show the exact import line, explain whether formatIso is a named or default export, include the one-line reason we prefer the shared util over the inline formatter, and list any bundle or circular-dependency risks a reviewer should watch for.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI replaced an inline formatter with an import from src/lib/date-utils.js and bundle size…+
I added an import and the app bundle grew unexpectedly
I replaced an inline formatter with an import from src/lib/date-utils.js and bundle size increased by 30KB. I don't know whether formatIso pulls in heavy dependencies. Who on the team decides acceptable bundle growth, what do I ask them, and what immediate steps can I take to check whether the import pulls in extra modules so I can revert or optimize?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross multiple features we keep importing small helpers instead of sharing a single…+
We keep proliferating small imports that bloat bundles
Across multiple features we keep importing small helpers instead of sharing a single lightweight utility, and bundle size creeps up. Where are we losing time and credibility — in local fixes, lack of bundle checks, or unclear ownership — and what policy and tooling change will stop this pattern without blocking everyday work?
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.