◆ JavaScript

Check if array includes value

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 taskBefore I add 'newTag' to the 'currentTags' array, check if 'newTag' is already in…+
Before I add 'newTag' to the 'currentTags' array, check if 'newTag' is already in 'currentTags'.
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 adding 'newTag' to the 'currentTags' array, I need to check if 'newTag' is already…+
Before adding 'newTag' to the 'currentTags' array, I need to check if 'newTag' is already present. This check should be case-insensitive, as users might type 'Red' or 'red' for the same tag, and we don't want duplicates based on capitalization.
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 tried to add 'Product A' to their cart, but it's already there. The current cart…+
A user is trying to add a duplicate item to their shopping cart.
A user just tried to add 'Product A' to their cart, but it's already there. The current cart array, 'cartItems', contains objects, and I need to check if an item with 'productId: 123' already exists before I add it again. If I don't catch this, the cart total will be wrong, and the user will be overcharged. What's the quickest way to check if an object with a specific 'productId' exists in 'cartItems', and if it does, what should be my next immediate action?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself needing to determine if a specific value or object exists within an…+
I keep writing custom loops to check if an item is in a list.
I frequently find myself needing to determine if a specific value or object exists within an array before performing an action, like adding a new tag or preventing a duplicate selection. I'm often writing custom loops, which feels inefficient and error-prone. What's a standard, readable approach I can consistently use to check for the presence of an item in an array, making my code cleaner and more reliable?
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.