◆ HTML

Select element by data attribute

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 taskI need to grab the 'data-product-id' from the main product display element so I can update the…+
I need to grab the 'data-product-id' from the main product display element so I can update the quantity in the cart. Make sure it's the one currently visible on the page.
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 this update live, I need to make sure the product ID selection is robust. It's…+
Before I push this update live, I need to make sure the product ID selection is robust. It's too easy for someone to accidentally grab the wrong 'data-product-id' if there are multiple similar elements. How can I make sure I always get the primary one being viewed?
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 deployed the new product page, and the 'add to cart' isn't working for some customers.…+
The new product page isn't correctly adding items to the cart, even though the 'data-product-id' seems present.
I just deployed the new product page, and the 'add to cart' isn't working for some customers. I'm trying to select the 'data-product-id' from the main product element, but sometimes a different, hidden product ID is being picked up instead. I can't tell if it's a timing issue or if the selector is too broad. What's the most reliable way to grab the correct, visible 'data-product-id' without breaking existing functionality?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly running into issues where my element selectors break when the page layout or…+
I keep struggling to reliably select specific elements on dynamic pages, leading to bugs.
I'm constantly running into issues where my element selectors break when the page layout or content changes slightly. It's costing us time in debugging and hotfixes. I need a more resilient approach to selecting elements by their 'data-attributes' on complex, dynamic pages. What habit should I change to build more robust selectors 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.