The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need this DOM element to visibly change when a user hovers and then revert when they leave. Make…
Execute — do the immediate task
+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.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I hand this to QA, make the hover animation obvious and reviewable: surface the transformed…
Improve — make it easier to accept
+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.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I just applied a hover function to card-17 and on quick mouse moves the animation flickers and…
Decide — diagnose the stuck moment
+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?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over many pages we implement tiny inline hover scripts like the one for card-17. They drift in…
Become — change the pattern
+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.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other programming language work people do in JavaScript.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.