◆ JavaScript

Manage component state

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 taskI need to wire a component so its UI stays in sync with user input and an async load. Update…+
I need to wire a component so its UI stays in sync with user input and an async load. Update the component state when the text input changes and when the fetch returns; prevent state updates after the component unmounts. After wiring, verify that typing reflects immediately and that the loaded data replaces the placeholder without causing errors.
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 commit this component, make the state handling easier for a reviewer: surface where…+
Before I commit this component, make the state handling easier for a reviewer: surface where local state lives, show which fields are derived vs source-of-truth, highlight any direct DOM reads or shared-mutable objects that could confuse updates, and flag code paths that might set state after unmount.
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 just saw a warning that state was updated after the component unmounted. The component…+
User types quickly then navigates away and I still get a setState warning
I just saw a warning that state was updated after the component unmounted. The component fetches profile data on mount and binds onChange for an input; Alice on QA left the page fast. I don't know whether the fetch or the input callback caused it, and I can't reproduce reliably. What is the most likely cause and the smallest change to reliably stop the warning while preserving behavior?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several features we keep getting state-update-after-unmount warnings and duplicated…+
setState warnings and spaghetti state across multiple components
Across several features we keep getting state-update-after-unmount warnings and duplicated state for the same entity in parent and child components. Each fix is ad hoc and we regress. Help me pick one habit to change that reduces these bugs and speeds reviews. Explain the habit and a concrete first PR-size change I can make.
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.