◆ JavaScript

Get child elements of selector

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 taskGet all the direct child elements of the 'main-content' div and store them in an array, so I…+
Get all the direct child elements of the 'main-content' div and store them in an array, so I can iterate over them to apply a specific style.
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 I start styling the 'product-card' elements, write a function that safely gets all…+
Before I start styling the 'product-card' elements, write a function that safely gets all direct children of a given DOM element, handling cases where the element might not exist or has no children, so I don't get null reference errors later.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to get the child elements of the 'user-profile-widget' container, but the array is…+
The new feature is breaking because I'm getting an empty list of children from a parent element that I know has them.
I'm trying to get the child elements of the 'user-profile-widget' container, but the array is empty even though I can see the children in the browser's inspector. This is happening intermittently. I'm afraid I'm missing a crucial lifecycle event or a race condition. What's the most likely reason for this, and what's the safest way to ensure I get all children once they're fully rendered?
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 issues where I try to access child elements too early, leading to 'null' or…+
I frequently struggle to reliably get DOM elements and their children when components render at different times.
I keep running into issues where I try to access child elements too early, leading to 'null' or empty lists, especially with dynamic content. This forces me to add fragile timeouts. What habit should I change to consistently ensure I'm only trying to access elements after they are guaranteed to be in the DOM?
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.