◆ HTML

Check if element contains a 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCheck if the 'featured-product' class is present on the main product image on the homepage, so…+
Check if the 'featured-product' class is present on the main product image on the homepage, so I can confirm the styling is applied correctly before the sale starts.
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 push the new pricing page live, I need to quickly verify if any of the 'sale-item'…+
Before I push the new pricing page live, I need to quickly verify if any of the 'sale-item' products are missing the 'limited-time-offer' class. We can't have products on sale without that visual indicator, or customers will miss the urgency. I need to know which ones to fix.
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 'Add to Cart' button on the product detail page isn't appearing for some users, according…+
A critical button isn't showing up for some users, and I can't reproduce it.
The 'Add to Cart' button on the product detail page isn't appearing for some users, according to customer support, but it works fine for me. I'm afraid we're losing sales. I suspect a JavaScript error is removing a critical class, but I don't know how to reliably check the live state of that element on their browser. How can I diagnose if the 'active-button' class is missing for those users, and what's the best way to pinpoint why?
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 get stuck when debugging why an element isn't styled correctly or behaving as…+
I often struggle to debug styling or behavior issues related to dynamic class changes.
I frequently get stuck when debugging why an element isn't styled correctly or behaving as expected, especially when classes are added or removed by JavaScript. I waste a lot of time guessing. What's the fundamental habit I need to develop to efficiently check an element's current classes and understand the dynamic changes happening on the page?
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.