◆ JavaScript

Manage user permissions

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 taskImplement a basic user authentication system for the internal dashboard so only logged-in…+
Implement a basic user authentication system for the internal dashboard so only logged-in employees can view project statuses, checking against our existing user database.
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 push this authentication system to production, harden it. It needs to handle failed…+
Before I push this authentication system to production, harden it. It needs to handle failed login attempts gracefully, implement secure password hashing, and include a session timeout for inactive users, because any security flaw here could expose sensitive project data to unauthorized eyes.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers are reporting that they are randomly logged out of the internal dashboard, often…+
Users are reporting that they are randomly logged out of the system, and I can't reproduce it reliably.
Users are reporting that they are randomly logged out of the internal dashboard, often mid-task, and I can't consistently reproduce the issue. It's happening to the sales team right before their client demos. I suspect a session management problem or a cookie issue, but I'm not sure where to start looking given the intermittent nature. The sales director is furious. What's the most effective way to pinpoint this intermittent logout bug, and what's the quickest way to stabilize it for the sales team?
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 building authentication and permission systems that are technically secure but often…+
I keep building authentication features that are secure but frustrating for users.
I keep building authentication and permission systems that are technically secure but often create friction for legitimate users, leading to support tickets and complaints from the marketing and sales teams. I prioritize security, but the user experience suffers. What habit should I change to balance strong security with a smooth, intuitive user experience, especially when implementing new access controls for sensitive data?
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.