◆ HTML

Get the value in an input text box

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
See the prompt↓All HTML tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGet the text that the user typed into the 'search-input' field when they click the…+
Get the text that the user typed into the 'search-input' field when they click the 'search-button'.
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 user submits, make sure we accurately capture whatever they've typed into the…+
Before the user submits, make sure we accurately capture whatever they've typed into the 'search-input' field. If we miss characters or get an old value, the search results will be wrong, leading to user frustration. Also, ensure it handles special characters correctly.
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 form submission is sending an empty string for the 'email-address' field, even though I…+
The form submission is sending an empty string for the 'email-address' field, even though I typed something in.
The form submission is sending an empty string for the 'email-address' field, even though I typed something in. I'm using an event listener, but it feels like I'm either grabbing the value too early, or there's a race condition. I'm afraid of missing user input. What's the most common pitfall when trying to get the current value from an input field, and what's the most reliable way to ensure I get the latest user input at the point of submission?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself debugging issues where user input from forms isn't correctly captured or is…+
I often find myself debugging issues where user input from forms isn't correctly captured or is missing.
I often find myself debugging issues where user input from forms isn't correctly captured or is missing, leading to incomplete data or broken features. This costs time and creates data integrity problems. What habit should I change in how I set up input capture to ensure I consistently get the correct, up-to-date value from any form field at the right moment, every time?
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.