◆ JavaScript

Build URL 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 taskConstruct the full API URL for the product search endpoint. Start from baseApi =…+
Construct the full API URL for the product search endpoint. Start from baseApi = https://api.internal.company.com/v1, append /products/search, add the q query with the searchTerm string, limit set to 25, and include the category if categoryId is a non-empty string. Ensure all query values are URL-encoded and return the final URL string.
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 hand the URL to the network team, make the important bits obvious: show the base,…+
Before I hand the URL to the network team, make the important bits obvious: show the base, path, each query key with its raw and encoded value, and highlight when the final URL exceeds 2048 characters. Flag missing searchTerm or an invalid categoryId format and propose the minimal change so a reviewer can approve without question.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur product search occasionally triggers 414 when users paste very long filters into the q…+
Search requests sometimes return 414 URI Too Long
Our product search occasionally triggers 414 when users paste very long filters into the q parameter. I build the URL by concatenating encoded parameters. I do not know whether to move to POST, truncate, or compress parameters. Given a public search box and occasional long queries, what is the likely best next move and the tradeoffs I should explain to the product manager?
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 patching URL construction code in multiple repos: different encoding functions,…+
Wasting time fixing ad-hoc URL builders across codebase
I keep patching URL construction code in multiple repos: different encoding functions, inconsistent parameter ordering, and scattered logic for optional params. It causes bugs and code review churn. What one pattern or shared utility should I introduce so future URL strings are correct and reviewers stop catching the same mistakes?
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.