◆ JavaScript

Declare a variable

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 taskDeclare a variable to hold the current user ID so the rest of the module can reference it. The…+
Declare a variable to hold the current user ID so the rest of the module can reference it. The variable should be named currentUserId, be block scoped, initially null, and include a one-line comment explaining why it is mutable.
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 push this change, make the variable declaration reviewer-friendly: explain when it…+
Before I push this change, make the variable declaration reviewer-friendly: explain when it becomes non-null, show the few lines of code that will assign it in the login flow, and flag any race conditions a reviewer should check for. Keep the comment concise and concrete.
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 declared currentUserId as let currentUserId = null and some tests now fail only under…+
I declared currentUserId and tests intermittently fail
I declared currentUserId as let currentUserId = null and some tests now fail only under concurrency. I suspect race conditions between token refresh and route guard. Who owns the sequence I need to coordinate with, what precise questions do I ask them, and what small code change will make the race visible in tests so I can fix it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOn this codebase we keep introducing module-level mutable variables like currentUserId and then…+
We scatter mutable module state across many files
On this codebase we keep introducing module-level mutable variables like currentUserId and then spend time hunting bugs when state diverges. Where is the real productivity loss — readability, testing, or initialization order — and what habit change and architectural rule would stop us from doing this again?
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.