◆ JavaScript

Propagate component props

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 taskPass props down to the card component so each instance shows different content. Given an array…+
Pass props down to the card component so each instance shows different content. Given an array products with objects having id, title, imgSrc, summary, iterate and call the component for each product, set a data-product-id attribute on the root element, and ensure title text is escaped and not injected as HTML.
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 ship this props propagation, make reviewer-friendly changes: surface where defaults…+
Before I ship this props propagation, make reviewer-friendly changes: surface where defaults are applied, document which prop is required (title), and add a validation step that logs a warning when a product lacks imgSrc so reviewers know why a placeholder appears. Keep the API plain JS objects so non-React engineers can reuse it.
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 loop products and mount cards, but after updating the products array the UI sometimes shows…+
Some cards show the previous product after re-render.
I loop products and mount cards, but after updating the products array the UI sometimes shows stale titles for a split second. The PM and the test engineer expect instant consistency. I can't tell if this is a diffing problem, a reuse bug, or event-handler closure holding old data. What is the likely cause and the best immediate change to ensure each mounted card always reflects its current props?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross feature work we often pass the same object references into components and then mutate…+
We keep reusing the same mutable objects as props and bug reports spike.
Across feature work we often pass the same object references into components and then mutate them, causing intermittent UI mismatches and confusing bugs. Where is the workflow breaking down and what single habit should the team adopt to reduce these prop-mutation bugs going forward?
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.