◆ JavaScript

Get unique array values

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI have an array of product IDs, but some are duplicated. Give me a new array with only the…+
I have an array of product IDs, but some are duplicated. Give me a new array with only the unique product IDs.
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 acceptI have an array of product IDs that might contain duplicates. I need a new array with only the…+
I have an array of product IDs that might contain duplicates. I need a new array with only the unique IDs. Also, ensure the order of the unique IDs in the new array is preserved from their first appearance in the original list, which is important for the display order on the page.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe category filter dropdown is showing duplicate entries, even though the backend is supposed…+
The dropdown list of categories shows duplicates, confusing users.
The category filter dropdown is showing duplicate entries, even though the backend is supposed to send unique categories. I'm looking at the 'rawCategories' array, and it definitely has repeats. The UX team is flagging this as a critical bug for the buyer experience. I need to quickly get a list of truly unique categories to populate the dropdown. What's the most efficient way to get only unique values from this array right now, and what's the first thing I should check if the problem persists after that?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly dealing with arrays from APIs, user selections, or local storage that contain…+
I frequently need to de-duplicate lists of items from various sources.
I'm constantly dealing with arrays from APIs, user selections, or local storage that contain duplicate entries, leading to redundant UI elements or incorrect calculations. It's a recurring task that slows down development. What's a reliable, idiomatic pattern I can consistently apply to efficiently get unique values from any array, saving me time and preventing these common data integrity issues?
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.