◆ JavaScript

Export a function

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 hand off this utility to the rest of the frontend team. Export the function default…+
I need to hand off this utility to the rest of the frontend team. Export the function default so imports are simple, keep the function name sensible for stack traces, and ensure the file still exports any other helpers used by the app. Make the export last in the file and add a one-line comment above it explaining intended use.
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 publish this module for the team, make the exported API obvious. Put the primary…+
Before I publish this module for the team, make the exported API obvious. Put the primary export at the bottom, surface the exported function name in the file top comment, and list secondary helpers together with brief one-line comments so a reviewer can grasp what they must import.
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 wired an import in App.js to use calculateDiscount but the console shows cannot find module.…+
I just saved the file and the import in App still fails to find the function
I wired an import in App.js to use calculateDiscount but the console shows cannot find module. I exported function calculateDiscount at the top as a named export, but other files expect a default. I'm worried changing the import will break customers. Should I convert calculateDiscount to a default export, change every consumer to named import, or add both export styles? Which has the least risk and what are the exact edits?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver the last quarter we waste time swapping imports because contributors mix default and named…+
We repeatedly ship modules where consumers are confused by default vs named exports
Over the last quarter we waste time swapping imports because contributors mix default and named exports across libraries. I want a habit that stops the churn: a short rule team members follow when adding exports, and a lightweight review checklist that flags mismatches. Suggest one team rule and two review checklist items that prevent this pain without blocking velocity.
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.