◆ JavaScript

Handle HTTP response

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 received a 502 from the user profile endpoint. Consume the response and map the JSON to the…+
I received a 502 from the user profile endpoint. Consume the response and map the JSON to the client model for display: profile.id, profile.name, profile.avatarUrl. If the response contains validation errors, show them inline; if it’s a server error, surface a friendly retryable message and log the raw response for debugging.
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 wire this response handler into the component, make it easy for QA to test: list the…+
Before I wire this response handler into the component, make it easy for QA to test: list the possible HTTP status cases and what the UI will show for each, extract the fields the UI cares about at top, and flag any ambiguous error messages that would confuse support engineers when they read the logs.
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 fetched the profile and the UI rendered avatarUrl as null although the API team says the…+
After parsing the response, the UI showed null for avatarUrl.
I fetched the profile and the UI rendered avatarUrl as null although the API team says the field is always present. I’m afraid my parser is swallowing nested properties or the server returned a different shape for some users. I can’t tell whether to adjust my mapping or request a schema fix. What is the most likely misread here and the immediate test I should run to decide the fix?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross projects I frequently patch response handlers to accommodate slightly different shapes:…+
Mapping inconsistencies between API and UI
Across projects I frequently patch response handlers to accommodate slightly different shapes: sometimes profile.avatar is a string, sometimes an object, sometimes missing. Those fixes pile up and tests become brittle. What habit or contract should I adopt to stop churning on these mappings, and what small guard or tool will enforce consistent shapes without blocking progress?
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.