◆ JavaScript

Remove item from array

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 taskRemove 'Out of Stock' from the list of available product filters on the search results page, so…+
Remove 'Out of Stock' from the list of available product filters on the search results page, so users only see relevant options.
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 daily inventory sync, ensure that any product marked 'discontinued' is completely…+
Before the daily inventory sync, ensure that any product marked 'discontinued' is completely removed from the active product catalog, not just hidden, so it doesn't accidentally reappear.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA user just reported that a comment they deleted reappeared on their profile after refreshing…+
A user reported seeing a deleted comment reappear on their profile after a page refresh.
A user just reported that a comment they deleted reappeared on their profile after refreshing the page. I thought my removal logic was sound, but clearly, something is off. Is the issue with the client-side state, the database update, or a caching problem? What's the fastest way to diagnose and fix this before more users experience it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI constantly write intricate code to remove items from arrays based on various conditions, and…+
I often find myself writing complex logic to remove items from lists, leading to subtle bugs.
I constantly write intricate code to remove items from arrays based on various conditions, and it frequently leads to off-by-one errors or unexpected side effects that surface later. What habit should I change to simplify my item removal logic and make it more robust, reducing the chance of introducing subtle bugs that are hard to track down?
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.