◆ HTML

Allow only numeric input in HTML text input

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 taskOn the new registration form, ensure the 'Phone Number' field only accepts numeric input so…+
On the new registration form, ensure the 'Phone Number' field only accepts numeric input so users don't enter letters before the launch on Friday.
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 new registration form goes live, make sure the 'Phone Number' field strictly…+
Before the new registration form goes live, make sure the 'Phone Number' field strictly enforces numeric input, including handling copy-pasted non-numeric characters. It needs to be user-friendly and prevent bad data from reaching the database.
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 new user registration form's phone number field is accepting letters, and the data team is…+
The new user registration form's phone number field is accepting letters, and the data team is worried about bad data.
The new user registration form's phone number field is accepting letters, and the data team is already flagging potential issues with our analytics. I'm afraid that relying solely on client-side validation won't be enough to stop all bad data, and it could lead to critical errors in our CRM. What's the most secure and comprehensive way to ensure only numeric input, including handling pasted text, and what should I tell the data team about our mitigation plan before the end of the day?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently find input fields accepting incorrect data types, leading to validation errors,…+
I often find input fields accepting incorrect data types, leading to backend issues and cleanup.
I consistently find input fields accepting incorrect data types, leading to validation errors, backend processing issues, and manual data cleanup. I waste time fixing these downstream problems. What habit should I change to establish more robust input validation practices from the start, ensuring data integrity without constant reactive fixes?
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.