◆ JavaScript

Run code in console

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 run this snippet in the browser console to reproduce a bug a user reported this…+
I need to run this snippet in the browser console to reproduce a bug a user reported this morning. Copy the code block below into the console, run it on the site at https://dashboard.acme.local, and tell me the exact console output and any uncaught errors. If it throws, include the stack trace and the line that failed so I can paste it into the issue.
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 paste this into the console for QA, make the snippet safer to execute in a live…+
Before I paste this into the console for QA, make the snippet safer to execute in a live session: wrap network calls so they can be stubbed, prevent it from modifying DOM outside #test-area, and add logging that shows input, output and elapsed time. Show the modified snippet and explain the three places a reviewer will hesitate.
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 pasted a short script into the client console on Chrome and there was no output and no…+
I pasted the snippet and nothing happened
I pasted a short script into the client console on Chrome and there was no output and no errors. The page has complex client-side routing and a token in localStorage. I worry the code ran in the wrong frame or before app bootstrap. What likely went wrong, how do I check which frame and timing, and what exact minimal change will show me whether the code executed where I expect?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross repeated debugging sessions I open the console, paste ad‑hoc snippets and later lose the…+
I keep reproing bugs by running quick snippets that later can't be reproduced
Across repeated debugging sessions I open the console, paste ad‑hoc snippets and later lose the exact state that reproduced the problem. Where am I losing time or credibility — in capturing environment, sequencing steps, or sharing reproducible inputs — and what three habits should I adopt to stop wasting time and to hand someone else a one‑click repro?
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.