◆ JavaScript

Validate an email address

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 taskI need to check if 'john.doe@example.com' is a valid email format before the user can proceed…+
I need to check if 'john.doe@example.com' is a valid email format before the user can proceed with registration.
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 their contact form, I need to validate the email address they entered.…+
Before the user submits their contact form, I need to validate the email address they entered. If it's not a standard email format, I need to prevent submission and tell them exactly what's wrong so they can fix it.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe're getting support tickets about users being unable to register, specifically with email…+
Some users are reporting that they can't sign up, even though they're entering what looks like a valid email address.
We're getting support tickets about users being unable to register, specifically with email validation failing for addresses that seem perfectly normal, like 'first.last+tag@domain.co.uk'. I'm using a standard regex, but it seems too strict for some real-world emails. I'm afraid we're rejecting legitimate users. What's the most robust way to validate email addresses without being overly restrictive and alienating users?
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 implementing email validation whenever I need to capture user emails, and I…+
I keep writing email validation logic from scratch for every new form or user input.
I'm constantly implementing email validation whenever I need to capture user emails, and I often find myself tweaking regular expressions or missing edge cases. This leads to inconsistent validation rules across the application and occasional user frustration. What habit should I change to standardize and improve the reliability of email validation across all user inputs?
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.