◆ JavaScript

Check string for substring

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 taskCheck if the user's input for their email address contains an '@' symbol before submitting the…+
Check if the user's input for their email address contains an '@' symbol before submitting the form, so we catch basic typos.
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 processing a user's new password, verify it contains at least one uppercase letter, one…+
Before processing a user's new password, verify it contains at least one uppercase letter, one number, and one special character, so we enforce strong security policies.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA customer just reported their order number, 'ORD-12345', isn't being recognized by the support…+
A customer reported that their order number isn't being recognized by the support chatbot.
A customer just reported their order number, 'ORD-12345', isn't being recognized by the support chatbot, which is supposed to identify 'ORD-' prefixes. I'm worried there's a subtle issue with how the chatbot is parsing or matching the string. Is it a case sensitivity problem, an extra space, or something else entirely? How can I quickly debug the exact string comparison logic to get this fixed for them?
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 write custom functions to check if a string contains specific patterns or substrings,…+
I frequently write custom string matching functions that are prone to edge cases and bugs.
I often write custom functions to check if a string contains specific patterns or substrings, and these frequently miss edge cases like leading/trailing spaces or different capitalizations. This leads to broken features and frustrated users. What habit should I change to make my string checking logic more resilient and less error-prone, reducing the time I spend debugging these small but critical issues?
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.