◆ JavaScript

Validate user 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 JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskUsers can submit the profile form with empty phone numbers. Add client-side validation that…+
Users can submit the profile form with empty phone numbers. Add client-side validation that checks phone is numeric and 10 digits, shows the error message under the field, and blocks submission until corrected. Coordinate with Priya in UX for the error copy and deploy the change by Tuesday.
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 hand this to QA, make the input validation reviewer-friendly: put the validation rules…+
Before I hand this to QA, make the input validation reviewer-friendly: put the validation rules at the top of the module, show the exact error strings next to each rule, and highlight any validators that accept malformed input like leading plus signs or spaces.
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 added a validator to the signup form and now some international users report their phone…+
validation rejects valid formatted numbers
I added a validator to the signup form and now some international users report their phone numbers are rejected. I wrote a strict 10-digit numeric rule because legal asked for consistency, but I don't know which countries we must accept. I can't change policy alone. What's the likely compromise that preserves compliance but doesn't block legitimate users, and how should I present this to legal and product?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe repeatedly lose time because validation rules live in many components, producing…+
validators scattered across files and inconsistent
We repeatedly lose time because validation rules live in many components, producing inconsistent error copy and duplicate bugs. Which habit should we adopt to centralize validation, how to version rules, and a lightweight gating step so changes don't break client or server expectations?
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 JavaScript'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.