◆ HTML

Select an element by name with jQuery

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 find the specific 'promo-code-input' field on the page so I can update its value…+
I need to find the specific 'promo-code-input' field on the page so I can update its value based on what the user types. This is for the Black Friday sale, so it needs to be working by Thursday.
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 send this to the client's procurement team, make it easy to approve -- surface the…+
Before I send this to the client's procurement team, make it easy to approve -- surface the savings figure up top, make pricing findable, flag what would make a reviewer hesitate.
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 marketing team just reported that the 'promo-code-input' isn't being updated when they…+
The marketing team says the promo code isn't applying correctly.
The marketing team just reported that the 'promo-code-input' isn't being updated when they paste a code, and the discount isn't applying. The campaign goes live tomorrow, and I'm worried we'll miss the sales window. I can't tell if the element isn't being found or if the update itself is failing. What's the most reliable way to target this specific input field, and what's the best next step to confirm it's being correctly selected?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time and credibility because I struggle to reliably select elements, especially…+
I frequently struggle with reliably selecting elements, especially when their IDs or classes change.
I keep losing time and credibility because I struggle to reliably select elements, especially when their IDs or classes are inconsistent or change without warning. This leads to broken functionality and last-minute fixes. What habit should I change to ensure I can always target the correct element on the page, even if the markup shifts, so it reads on a phone?
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.