◆ JavaScript

Create array containing range

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 taskCreate a list of numbers from 1 to 10, including both, to represent the pages in the…+
Create a list of numbers from 1 to 10, including both, to represent the pages in the report.
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 acceptWhen generating the page navigation for the quarterly report, make sure it covers all pages…+
When generating the page navigation for the quarterly report, make sure it covers all pages from the first to the last, so users can easily jump to any section without missing anything.
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 pagination on the new client dashboard is showing '1, 3, 5...' instead of consecutive…+
The pagination on the client's new dashboard is skipping numbers.
The pagination on the new client dashboard is showing '1, 3, 5...' instead of consecutive numbers. I'm afraid it's confusing the client and making them think data is missing. I can't tell if it's a display error or if the underlying page list is actually incomplete. What's the most likely reason for this kind of pagination error and what's the best way to quickly verify the sequence of numbers being generated?
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 manually generating sequences of numbers for things like pagination,…+
I keep having to manually create sequences of numbers for lists and indices.
I frequently find myself manually generating sequences of numbers for things like pagination, indices, or date ranges, and it's often a source of off-by-one errors or missed values. This wastes time and introduces subtle bugs. What habit should I change to more reliably and efficiently create accurate numerical ranges for these common tasks?
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.