◆ JavaScript

Add elements to array beginning

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 taskAdd 'newFeature' to the start of the 'featuresList' array in the 'config.js' file, making sure…+
Add 'newFeature' to the start of the 'featuresList' array in the 'config.js' file, making sure the existing features shift correctly.
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 'newFeature' to 'featuresList', check if it already exists to prevent duplicates,…+
Before adding 'newFeature' to 'featuresList', check if it already exists to prevent duplicates, and then add it to the beginning if it's not there, so we don't accidentally break the build with redundant entries.
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'm pushing a security patch to the 'dependencies' array, but it's not showing up in the…+
I just tried to add a critical security patch to the 'dependencies' array, but the build failed silently and I'm not seeing the new entry in the deployed code.
I'm pushing a security patch to the 'dependencies' array, but it's not showing up in the deployed code and the build logs are clean. I'm worried I've messed up the array manipulation and the vulnerability is still open. What's the most likely reason for this silent failure and what's the safest way to ensure my patch is actually at the beginning of the array?
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 debugging unexpected behavior after adding elements to the beginning…+
I keep introducing subtle bugs when I modify arrays at the start, especially with complex objects.
I frequently find myself debugging unexpected behavior after adding elements to the beginning of arrays, particularly when dealing with nested objects. I lose so much time tracking down these elusive issues. What habit should I change to ensure array modifications at the start are always robust and predictable, preventing these recurring headaches?
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.