◆ JavaScript

Check for empty string

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 taskBefore sending the user's email address to the server, check if the email input field is…+
Before sending the user's email address to the server, check if the email input field is completely empty.
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 acceptWhen the user submits the contact form, check if the 'message' field is empty. If it is, show…+
When the user submits the contact form, check if the 'message' field is empty. If it is, show an error message 'Please enter your message' next to the field and prevent the form from submitting.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur new user registration form is submitting even when the 'username' field looks empty to the…+
The form is submitting even when a required text field appears empty to the user.
Our new user registration form is submitting even when the 'username' field looks empty to the user. I'm checking for an empty string, but it seems to be passing. I'm afraid we're creating accounts with invalid data. Is it possible there are hidden characters or whitespace, and what's the most robust way to check for true emptiness before allowing 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'm consistently finding that my 'empty' checks for user input fields are too simplistic,…+
I keep missing edge cases for 'empty' inputs, leading to bad data.
I'm consistently finding that my 'empty' checks for user input fields are too simplistic, allowing whitespace-only strings or other non-visible characters to pass. This leads to dirty data in the database. What habit should I change to ensure my input validation for emptiness is truly robust 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.