◆ JavaScript

Set request headers

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 set request headers for an API call to the internal billing service. Add…+
I need to set request headers for an API call to the internal billing service. Add Authorization with the bearer token stored in sessionToken, Content-Type as application/json, and a custom header X-Client-Version with value 3.2.1. Ensure the headers object exists and that header names are normalized so the service accepts them before the request is sent.
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 billing, make it impossible for the reviewer to miss…+
Before I send this request to billing, make it impossible for the reviewer to miss authentication or content issues. Surface missing or empty values for sessionToken, Content-Type, or X-Client-Version, coalesce duplicate header names, and highlight if any header value exceeds 1KB. Return a concise summary and a ready-to-attach headers object.
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 just sent an authenticated request to the billing service and got a 401. I set Authorization…+
The API returned 401 on a request that previously worked
I just sent an authenticated request to the billing service and got a 401. I set Authorization from sessionToken and left Content-Type as application/json. The token was created an hour ago; I do not know whether it expired or was malformed. My deploy went out yesterday so no recent code changes on my side. What is the most likely cause and the next practical checks and fixes I should run now?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several projects we keep getting flaky authentication or rejection errors caused by…+
Repeated errors from services complaining about headers
Across several projects we keep getting flaky authentication or rejection errors caused by headers: tokens occasionally missing, header casing inconsistent, and debug headers accidentally shipped. I spend time hunting each failure on Friday deployments. What habit or small process should I adopt so headers are consistently correct and these incidents stop taking my Fridays?
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.