◆ C#

Manage group-based licensing

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 taskAssign the 'Developer Tools' licensing group to the new hires, Sarah and John, ensuring they…+
Assign the 'Developer Tools' licensing group to the new hires, Sarah and John, ensuring they get access to all the necessary IDEs and debugging tools. Then, remove Mark from the 'Legacy Systems Access' group, as he's no longer working on those projects.
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 onboard the new batch of interns, make sure the 'Intern Developer' licensing group…+
Before I onboard the new batch of interns, make sure the 'Intern Developer' licensing group grants access only to the necessary development environments and no sensitive production data. Flag any permissions that seem overly broad or unnecessary for their roles, so we maintain least privilege.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new contractor, Emily, just started, and she needs access to the 'Payments API' group to…+
A new contractor just started, and they need access to the 'Payments API' group, but I'm unsure if their contract includes that level of access.
A new contractor, Emily, just started, and she needs access to the 'Payments API' group to begin her work, but I'm unsure if her contract includes that level of access. Our security policy is very strict about external access to payment systems, and I can't tell if granting it now would violate compliance. Who needs to approve this, and what's the quickest way to get a definitive answer without delaying her start?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself manually reviewing individual user permissions after group changes,…+
I frequently find myself manually reviewing individual user permissions after group changes, wasting time and risking errors.
I frequently find myself manually reviewing individual user permissions after group changes, wasting time and risking errors. It feels like our group-based licensing isn't always granular enough, or I'm missing a step. What habit should I change to ensure that when I modify group memberships, the resulting individual permissions are always correct and compliant without needing a manual audit every time?
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 C#'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.