◆ JavaScript

Receive command line arguments

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 taskWrite the code to read the first two command line arguments passed to this script, assuming…+
Write the code to read the first two command line arguments passed to this script, assuming they are 'username' and 'environment', so I can use them to configure the database connection.
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 I finalize the deployment script, write a robust way to parse command line arguments. I…+
Before I finalize the deployment script, write a robust way to parse command line arguments. I need to accept a 'mode' (required, 'dev' or 'prod'), an optional 'port' (default 3000), and a flag 'verbose'. It should provide helpful error messages if required arguments are missing or invalid, so the operations team doesn't get stuck.
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 build script failed on staging, saying 'environment' argument is missing, but it works on…+
The build script failed on the staging server because it couldn't find a required configuration value, but it works locally.
The build script failed on staging, saying 'environment' argument is missing, but it works on my machine and I'm sure I'm passing it. The error message is generic. I can't tell if the argument isn't being passed correctly by the CI system, or if my script is misinterpreting it, or if there's a different parsing issue on the server. What's the best way to diagnose why my script isn't seeing the 'environment' argument on staging, and how can I make my argument parsing more resilient?
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 waste hours debugging why my scripts aren't picking up command line arguments…+
I spend too much time debugging scripts that fail because of malformed or missing command line arguments.
I frequently waste hours debugging why my scripts aren't picking up command line arguments correctly, especially when they move between environments or when new team members use them. This leads to deployment delays and frustration. What habit should I change to make my command line argument handling more predictable and less error-prone across different contexts?
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.