◆ JavaScript

Implement role-based access control

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 taskAdd a new 'Editor' role to the user management system, granting access to modify content but…+
Add a new 'Editor' role to the user management system, granting access to modify content but not publish it, and apply it to Sarah and David.
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 implement this new role-based access control for the customer portal, make sure it's…+
Before I implement this new role-based access control for the customer portal, make sure it's robust against common privilege escalation attacks and that the new roles align with our existing business operations, flagging any potential security gaps.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentAfter deploying the new 'Manager' role, some users are reporting they can't access reports they…+
After deploying the new 'Manager' role, some users are reporting they can't access reports they used to see, but others can.
After deploying the new 'Manager' role, some users are reporting they can't access reports they used to see, but others can. I'm afraid of a security vulnerability if I've misconfigured permissions, or worse, a data breach. The compliance team is asking for an update by tomorrow. I can't tell if it's a caching issue or an incorrect permission mapping. What's the likely diagnosis and the best next move to resolve this without exposing sensitive data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently have to manually adjust permissions for new roles or when roles change, leading…+
We frequently have to manually adjust permissions for new roles or when roles change, leading to errors and delays.
We frequently have to manually adjust permissions for new roles or when roles change, leading to errors and delays. This often results in users having too much or too little access, creating security risks or workflow bottlenecks. What habit should I change to automate permission assignments and ensure consistency across all user roles?
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.