◆ JavaScript

Animate element style

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 DOM element to visibly change when a user hovers and then revert when they leave.…+
I need this DOM element to visibly change when a user hovers and then revert when they leave. Make the style changes in a function I can call so I can attach it to mouseenter and mouseleave for the element with id card-17. Ensure transitions are smooth and the function only touches transform and opacity so other inline styles stay intact.
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 hand this to QA, make the hover animation obvious and reviewable: surface the…+
Before I hand this to QA, make the hover animation obvious and reviewable: surface the transformed end-state in comments, keep the timing under 200ms, and flag any properties that will cause layout thrashing. Make the function accept an element node so testers can call it on card-17 or similar cards.
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 applied a hover function to card-17 and on quick mouse moves the animation flickers and…+
Hover animation flickered in Chrome when multiple transitions ran.
I just applied a hover function to card-17 and on quick mouse moves the animation flickers and resets. The users are front-end devs and a product designer who expects smooth motion. I don't know whether the issue is conflicting CSS transitions or my JS reassigning styles. What is the most likely cause and the smallest code change to stabilize the hover without removing existing inline styles?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver many pages we implement tiny inline hover scripts like the one for card-17. They drift in…+
We keep adding one-off hover functions across the app.
Over many pages we implement tiny inline hover scripts like the one for card-17. They drift in timing and break when designers change CSS. Where are we losing time and why do these bitwise fixes keep returning? Recommend one habit or rule to adopt so future hover changes are predictable and quick to implement.
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.