◆ JavaScript

Parse query parameters

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.

3prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AImprove — make it easier to acceptBefore this hits the handler team, make the query parsing easy to audit. Put the important…+
Before this hits the handler team, make the query parsing easy to audit. Put the important values up front: show raw query string, parsed keys, coercions applied, defaults used, and any validation failures. Flag any unknown parameters and suggest whether they look like a typo of expected keys. Return a clean params object plus a one-line summary for the reviewer.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentI invoked a page and the handler threw an error because userId parsed to NaN. The URL came from…+
Handler threw for invalid userId from query
I invoked a page and the handler threw an error because userId parsed to NaN. The URL came from a marketing email link. I validated my parsing code and it looks straightforward, but I do not know whether the campaign inserted broken links or whether our parser mishandled PLUS signs and encodings. What is the most likely diagnosis and the immediate tests to confirm and fix it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CBecome — change the patternOver the last quarter I keep patching route handlers for query parsing edge cases: different…+
Spending time fixing inconsistent query parsing across routes
Over the last quarter I keep patching route handlers for query parsing edge cases: different encoding, missing defaults, and inconsistent validation. Each fix is small but I waste time. Which single change or coding standard should I adopt to stop this recurring churn and make new handlers reliable out of the box?
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.