◆ JavaScript

Loop through object properties

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFor the 'productDetails' object, list each property name and its value so I can see everything…+
For the 'productDetails' object, list each property name and its value so I can see everything it contains.
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 sending the product data to the analytics team, go through each piece of information…+
Before sending the product data to the analytics team, go through each piece of information about the new widget, make sure every detail is included, and flag any empty fields so we don't miss anything important.
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 new product page for the 'Titan X' isn't showing the warranty information or the material…+
The product page isn't displaying all the expected details, and I suspect missing data.
The new product page for the 'Titan X' isn't showing the warranty information or the material specs. I'm worried a critical piece of data is missing or misnamed, preventing it from appearing. I can't tell if the data wasn't provided or if the system just isn't finding it. How do I quickly check all the available data points for the 'Titan X' and identify any missing or incorrectly labeled fields?
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 spending time manually checking data objects to ensure all expected properties…+
I often spend too much time manually checking data structures for completeness.
I'm constantly spending time manually checking data objects to ensure all expected properties are present and filled before they're used in the UI or sent to other systems. This is slow and error-prone. What habit should I change to more efficiently verify the completeness and structure of data objects, especially when dealing with new features or external integrations?
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.