◆ JavaScript

Manage authentication flow

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWe have to get login working for the mobile web client by Wednesday. Implement the…+
We have to get login working for the mobile web client by Wednesday. Implement the authentication flow that accepts email and password, sends them to the server for a session token, stores the token in a secure, non-accessible cookie, refreshes the token before expiry, and redirects to the dashboard on success. Failures should show a clear error message without exposing server internals.
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 auth to the security reviewer, make the flow easy to verify: add a visible token…+
Before I hand auth to the security reviewer, make the flow easy to verify: add a visible token expiry countdown in dev mode, document which endpoints exchange credentials and which set cookies, surface where tokens are stored and why (cookie vs localStorage), and flag any places that still read the raw token directly in client code.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSome users report they get logged out when they reload the app. The server issues short-lived…+
Users are intermittently logged out on page reload.
Some users report they get logged out when they reload the app. The server issues short-lived session tokens and we store them in a secure cookie, but we also recently added an iframe that hits an auth-heavy endpoint. I suspect SameSite or cookie path issues or that the refresh-before-expiry logic doesn’t run for cold loads. I can’t reproduce reliably. What are the most likely causes and the quickest checks to confirm whether cookies, SameSite, or missing refresh calls are to blame?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several releases we keep introducing session reliability problems: token expiry…+
Authentication bugs keep breaking user sessions across updates.
Across several releases we keep introducing session reliability problems: token expiry handling, inconsistent storage between SPA and legacy pages, and refresh race conditions. These cause support tickets and urgent patches. Which two practices or small technical boundaries should we adopt to reduce these issues — one change to the auth codebase and one process change for future work?
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.