◆ JavaScript

Parse JSON string

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 have a webhook that receives a JSON payload from Stripe and sometimes throws when the body is…+
I have a webhook that receives a JSON payload from Stripe and sometimes throws when the body is malformed. Parse the incoming body string into an object, validate the required fields customer_id and amount exist and are numbers, and if parsing fails respond 400 with a clear message so the caller can fix it.
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 webhook handler to the ops team, make the payload validation easy to audit:…+
Before I send this webhook handler to the ops team, make the payload validation easy to audit: place the parse and schema check at the top, surface the exact offending key and value, and call out where optional fields could be abused. Flag any try/catch that swallows errors without a 400 response.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA Stripe webhook started failing for some customers; the handler throws a SyntaxError when…+
A webhook crashed with SyntaxError parsing JSON
A Stripe webhook started failing for some customers; the handler throws a SyntaxError when JSON.parse runs and I return 500 to Stripe. I don’t know if the problem is bad data from Stripe or an upstream proxy mangling the body. What is the most likely cause and the safest immediate change so we return a helpful 400 and log the raw body for debugging?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery few weeks a third-party webhook arrives with broken JSON and I end up adding ad hoc fixes…+
Repeated parsing errors from external payloads
Every few weeks a third-party webhook arrives with broken JSON and I end up adding ad hoc fixes for each case. This wastes time and leaves us exposed. What process and simple code pattern should I make standard so incoming JSON is parsed defensively, validated against a schema, and incidents surface actionable debug info without leaking PII?
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.