◆ JavaScript

Toggle CSS class

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 taskMake the follow-button toggle visually clear. When the user clicks Follow, add the CSS class…+
Make the follow-button toggle visually clear. When the user clicks Follow, add the CSS class is-following to the button element and change its label to Following; when they click Unfollow, remove is-following and set label to Follow. Make sure the class change happens immediately for responsiveness, and only after the server confirms do we persist the new status in the profile object.
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 ask design to sign off, make the toggle robust for slow networks. Ensure the…+
Before I ask design to sign off, make the toggle robust for slow networks. Ensure the is-following class and label change instantly on click, show a small spinner overlay while waiting for the server, and revert the class plus show an error toast if the API call fails. Call out any edge cases where double-clicking would cause class toggles to flip incorrectly so the reviewer can assess UX risk.
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 hit Follow fast twice out of habit; the button now reads Following but my network trace shows…+
I clicked Follow twice and the button shows the wrong state
I hit Follow fast twice out of habit; the button now reads Following but my network trace shows the unfollow call succeeded last. I don't know if my click handlers are racing or if the optimistic toggle and the server response flipped things in the wrong order. What's the most likely cause and what minimal change prevents this double-click flip without blocking responsiveness?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternFrequent user reports say toggles flicker or show the opposite state when connectivity is poor.…+
We keep shipping toggles that mislead users under flaky networks
Frequent user reports say toggles flicker or show the opposite state when connectivity is poor. Each time we add ad-hoc guards per component. What developer habit should we change to stop this pattern, and which small shared utility would you introduce so every toggle behaves the same under latency and failure?
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.