◆ HTML

Apply inline CSS for hover states

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 taskApply a hover state to the 'submit-button' so its background color changes to '#0056b3' when…+
Apply a hover state to the 'submit-button' so its background color changes to '#0056b3' when moused over.
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 the design team reviews this form, apply a hover state to the 'submit-button' so its…+
Before the design team reviews this form, apply a hover state to the 'submit-button' so its background color changes to '#0056b3'. They always expect interactive elements to have clear visual feedback, and I want to make sure this meets their standards without any last-minute changes.
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 QA team just reported the 'submit-button' doesn't show any hover state, even though I added…+
The QA team just reported that the 'submit-button' doesn't show any visual change when hovered over.
The QA team just reported the 'submit-button' doesn't show any hover state, even though I added the inline CSS. I've checked for typos, but it seems correct. Could another style be overriding it, or is there a browser compatibility issue? I'm afraid of messing up the existing styles if I try to force it.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently struggle with getting hover states and other small interactive elements to behave…+
I frequently struggle with getting hover states and other small interactive elements to behave consistently across browsers.
I frequently struggle with getting hover states and other small interactive elements to behave consistently across browsers, leading to inconsistencies and extra debugging time. It feels like a constant battle against browser quirks. What habit can I change to ensure these small interactive details are robust from the start?
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 HTML'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.