◆ JavaScript

Detect undefined object property

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.address' property exists before trying to display it on the profile…+
Check if the 'user.address' property exists before trying to display it on the profile page.
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 rendering the user's 'shippingInfo', first check if the 'shippingInfo.address' property…+
Before rendering the user's 'shippingInfo', first check if the 'shippingInfo.address' property exists and is not null or an empty string, so we can display a 'No address provided' message instead of an error or blank space.
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 'userProfile' component just threw an error for a customer because it tried to access…+
The 'userProfile' component just crashed for a customer because it tried to access 'user.preferences.theme' and 'preferences' was missing.
The 'userProfile' component just threw an error for a customer because it tried to access 'user.preferences.theme', but the 'preferences' object itself was entirely missing for that user. I'm afraid this is breaking the UI for many users who haven't set their preferences yet. What's the quickest, safest way to check if 'user.preferences' exists before trying to access any of its nested properties, so we can prevent these crashes immediately?
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 get runtime errors when accessing deeply nested object properties because I forget to…+
I consistently forget to check for the existence of nested object properties, leading to frequent runtime errors.
I often get runtime errors when accessing deeply nested object properties because I forget to check if intermediate properties exist, causing our application to crash for users. This impacts reliability. What habit should I change to ensure I always robustly check for the existence of every level of a nested object property, preventing these frustrating and predictable crashes?
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.