◆ JavaScript

Determine virtual features

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 taskAdd a 'share to Twitter' button next to the blog post title, so readers can easily spread the…+
Add a 'share to Twitter' button next to the blog post title, so readers can easily spread the word.
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 we launch the new user dashboard, make sure the 'export data' button is clearly visible…+
Before we launch the new user dashboard, make sure the 'export data' button is clearly visible and that the 'settings' gear icon is intuitive, so users can find key functions without hunting around.
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 product owner just asked for a 'favorite article' button, but I'm torn on placement. Should…+
The product owner wants a new 'favorite' button for articles, but I'm not sure where it should live.
The product owner just asked for a 'favorite article' button, but I'm torn on placement. Should it be next to the title, in the sidebar, or at the bottom? I'm worried about cluttering the UI, but also want it to be discoverable. What's the best spot to maximize usage without overwhelming the reader? I need to propose a solution by our stand-up.
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 building new features that users barely touch, leading to wasted effort and missed…+
I frequently implement new features that users don't engage with as expected.
I keep building new features that users barely touch, leading to wasted effort and missed deadlines. I often assume I know what's best. What habit should I change to better validate feature ideas and placement with real users earlier in the process, ensuring I build what they actually need and will use?
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.