◆ JavaScript

Filter array items

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 remove inactive users from an array before sending notifications. Filter the users…+
I need to remove inactive users from an array before sending notifications. Filter the users array to include only those with isActive true and a lastSeen timestamp within the past 90 days. Return the filtered array ready for the notifications job.
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 the notifications run tonight, make the filter easy to audit. Put the final count…+
Before the notifications run tonight, make the filter easy to audit. Put the final count comment above the snippet, show the filter condition clearly (isActive and lastSeen window), and flag edge cases like missing lastSeen or clock skew. Keep the code short and explicit so an operations reviewer can verify it quickly.
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 filtered users but notifications still went to accounts marked inactive. The operations…+
Notifications went to inactive accounts
I just filtered users but notifications still went to accounts marked inactive. The operations manager, Lee, is upset. I’m uncertain whether lastSeen was missing or the isActive flag is inconsistent in the DB. What’s the most likely reason and the immediate safe fix to prevent more unwanted notifications tonight?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep having mismatched filter criteria between the API, the worker, and the analytics job,…+
Filter logic drifting between services
We keep having mismatched filter criteria between the API, the worker, and the analytics job, so reports and jobs disagree on who is active. It undermines trust and causes repeated firefights. Which single pattern will stop this — a shared utility function, schema-enforced user state, or documented business rule in a central place? Recommend the change and how to get the team to adopt it.
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.