◆ JavaScript

Check if variable is 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 taskCheck if the 'userName' variable is a string before attempting to convert it to…+
Check if the 'userName' variable is a string before attempting to convert it to uppercase.
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 validating the 'promoCode' field on the checkout page, ensure it's a string and not empty,…+
When validating the 'promoCode' field on the checkout page, ensure it's a string and not empty, and if it's not valid, display an error message below the input field.
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 user profile update is crashing when 'zipCode' is submitted, showing 'toUpperCase is not a…+
The user profile update is failing when the 'zipCode' field is submitted, and the console shows a 'toUpperCase is not a function' error.
The user profile update is crashing when 'zipCode' is submitted, showing 'toUpperCase is not a function'. I'm worried a number or null value is getting through, and it's breaking the entire form. What's the most accurate and reliable way to check if a variable is specifically a string type, and what's the best practice for handling type mismatches gracefully in form submissions?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep running into runtime errors because I'm not consistently checking the type of variables…+
I frequently encounter type errors because I assume a variable is a string, but it turns out to be something else.
I keep running into runtime errors because I'm not consistently checking the type of variables before performing string operations. This leads to unexpected crashes and debugging headaches. What's a better habit or pattern I can adopt to reliably confirm if a variable is a string, and how can I integrate this into my validation routines to prevent these common type-related bugs?
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.