◆ JavaScript

Attach event listener

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 this button on the product page to trigger the cart flow. Add an event listener so…+
I need this button on the product page to trigger the cart flow. Add an event listener so clicking Add to Cart calls addToCart with the product id, and ensure the listener is attached only once when the page initializes on Thursday morning.
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 wire this up to procurement, make the click handler frictionless for reviewers: show…+
Before I wire this up to procurement, make the click handler frictionless for reviewers: show the product id where the handler is bound, put the actual callback name addToCart at the top, and flag any closures capturing large objects that could leak memory.
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 just attached the click handler for Add to Cart on the product page; QA reports the handler…+
I wired the button and it's firing twice
I just attached the click handler for Add to Cart on the product page; QA reports the handler runs twice when clicked. I bound the listener inside the render function and the component re-renders; the product manager is waiting. I can't inspect the full render cycle in their staging environment. Likely cause and best fix to stop the duplicate calls?
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 pages we keep getting duplicated event handlers after users navigate back and…+
handlers multiply after repeated navigation
Across several pages we keep getting duplicated event handlers after users navigate back and forth. This costs time debugging and causes cart duplication bugs. Which habit should the team adopt to stop these regressions: where to register listeners, how to structure teardown, and one small lint or code-review rule to catch it early?
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.