◆ JavaScript

Create HTTP request

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 taskI need to POST JSON to https://api.example.com/v1/orders to create order 9045. Include…+
I need to POST JSON to https://api.example.com/v1/orders to create order 9045. Include Authorization Bearer token stored in auth.token, send Content-Type application/json, and retry once on network failure. Return the parsed JSON response so I can update the UI immediately.
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 send this request to the payments API, make it easy for a reviewer to approve: surface…+
Before I send this request to the payments API, make it easy for a reviewer to approve: surface the exact headers and body up front, highlight any sensitive fields being sent, show the retry logic and timeout value, and flag anything that would make a procurement reviewer hesitate such as using a non-HTTPS URL or long timeouts.
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 posted to the orders endpoint for order 9045 and the call timed out three times. The payment…+
The request to create an order timed out repeatedly.
I posted to the orders endpoint for order 9045 and the call timed out three times. The payment team says their endpoint is healthy. I’m worried my timeout is too short, or my request body is malformed causing the server to hang. I can’t tell whether the failure is client-side networking, my headers, or a server-side problem. What checks should I perform in order to diagnose and the best immediate next action to get the order created safely?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time chasing intermittent HTTP failures: requests that succeed locally but fail…+
Repeated intermittent network failures
I keep losing time chasing intermittent HTTP failures: requests that succeed locally but fail in CI or on staging, and I often blame timeouts or retries without proof. Where am I wasting time in my current request patterns, and what changes to error handling, timeouts, or local tooling will reduce firefights and make failures actionable?
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.