◆ JavaScript

Manage cookies

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 taskSet a cookie named sessionId with value from sessionIdVar that expires in seven days, is…+
Set a cookie named sessionId with value from sessionIdVar that expires in seven days, is flagged HttpOnly and Secure, and set SameSite to Lax. Also update the cookie store so subsequent requests during this session see the new value. Ensure you do not overwrite an existing persistent preference cookie named userPrefs.
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 deploy this cookie change, make it easy for the privacy reviewer to approve. Show…+
Before I deploy this cookie change, make it easy for the privacy reviewer to approve. Show which cookies will be created or updated, their expirations, security flags, and whether any conflict exists with cookies already set: particularly userPrefs and analytics_id. Highlight any cookie that is not HttpOnly or Secure and explain the privacy risk in one sentence.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSeveral users say they get logged out mid-session. I set sessionId as a seven-day cookie with…+
Users report being logged out unexpectedly
Several users say they get logged out mid-session. I set sessionId as a seven-day cookie with HttpOnly and Secure flags. I do not know if a reverse proxy or missing domain attribute is clearing it, or if browsers reject SameSite settings. What checks should I run now to pinpoint whether cookies are being dropped by server headers, proxy stripping, or browser policy?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross builds I spend hours chasing cookie problems: domain mismatches, environment-specific…+
Debugging cookie issues across environments takes hours
Across builds I spend hours chasing cookie problems: domain mismatches, environment-specific cookie policies, and test suites that don't simulate secure contexts. It costs time and causes flaky auth bugs. What concrete change in how I set and test cookies will cut this debugging time and make deployments reliable?
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.