◆ JavaScript

Develop web-accessible software

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 taskGet the new user signup flow working on the staging server by Friday so the QA team can start…+
Get the new user signup flow working on the staging server by Friday so the QA team can start testing. Make sure the form validation is robust for all fields and that the data saves correctly to the database.
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 new user signup flow to staging, make sure it's accessible to screen readers…+
Before I push this new user signup flow to staging, make sure it's accessible to screen readers and keyboard navigation. Also, optimize the image sizes so it loads fast on a phone, and check for any console errors that might trip up a user.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new user signup flow is failing intermittently in staging, but I can't replicate it…+
The new user signup flow is failing intermittently in staging, but I can't replicate it consistently on my local machine.
The new user signup flow is failing intermittently in staging, but I can't replicate it consistently on my local machine. Priya from QA is reporting a 'server error' on submission, but the logs show success. I'm afraid of pushing a broken feature to production. What's the most likely cause of this intermittent failure, and what's the best next step to diagnose it without holding up the release?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time debugging issues that only appear in staging or production, not on my local…+
I keep losing time debugging issues that only appear in staging or production, not on my local setup.
I keep losing time debugging issues that only appear in staging or production, not on my local setup. My local environment often doesn't perfectly mirror production, leading to surprises. What habit should I change to ensure my local testing catches more of these environment-specific bugs before they hit QA?
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.