◆ JavaScript

Update UI 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 taskThe dashboard's filters must reflect the current selection immediately. When a user toggles any…+
The dashboard's filters must reflect the current selection immediately. When a user toggles any filter control, update the UI state object filters.selected and re-render the list with the new predicate. Debounce the heavy list render by 150ms but ensure the filter controls show their active state instantly. If the new filter yields zero results, show a contextual message guiding the user to broaden filters.
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 the filter UI, make the active choices readable at a glance. Move the summary of…+
Before I ship the filter UI, make the active choices readable at a glance. Move the summary of applied filters to the top, expose the total result count, and make the primary filter control visually dominant. Flag any filter combinations that will trigger a full data fetch or that disable client-side caching so the reviewer knows where performance will degrade.
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 clicked the 'Only open tasks' toggle; the button showed active but the task list still showed…+
I toggled a filter and the list didn't update, but controls appeared active
I clicked the 'Only open tasks' toggle; the button showed active but the task list still showed closed items and the count didn't change. My peers will say the UI is broken. I can't tell if the state object didn't update, the render was skipped, or the filter predicate is wrong. What's the most likely failure mode and the step I should check first to isolate it within 10 minutes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross multiple features, rapid sequence interactions leave the UI in surprising states:…+
We spend time debugging inconsistent UI states after rapid interactions
Across multiple features, rapid sequence interactions leave the UI in surprising states: controls look active but views lag or show wrong data. We repeatedly patch individual handlers. What single habit should the team adopt to cut down these incidents, and what lightweight architecture change will make state transitions deterministic and easier to debug?
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.