◆ C#

Conduct audit and compliance tasks

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 C# tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGenerate the access log report for all production servers for the last 90 days, specifically…+
Generate the access log report for all production servers for the last 90 days, specifically for users with administrative privileges, and provide it to the external auditors by Friday morning.
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 submit this quarterly compliance report to the regulatory body, ensure all sensitive…+
Before I submit this quarterly compliance report to the regulatory body, ensure all sensitive customer data is properly masked or anonymized in the generated logs. Highlight any instances where PII might still be exposed.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe auditors just asked for a detailed breakdown of all changes made to the firewall rules in…+
The auditors just asked for a detailed breakdown of all changes made to the firewall rules in the last six months, and our current logging system only keeps a high-level summary.
The auditors just asked for a detailed breakdown of all changes made to the firewall rules in the last six months, and our current logging system only keeps a high-level summary. I'm afraid this will look like we're not compliant, but I don't know how to reconstruct that level of detail from our existing backups. I can't tell them we only implemented detailed logging last month. What's the likely diagnosis here and the best next move?
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 struggle to correlate security incidents with specific user actions across…+
I frequently struggle to correlate security incidents with specific user actions across disparate logging systems.
I frequently struggle to correlate security incidents with specific user actions across disparate logging systems, often delaying incident response during an audit. This always makes me feel unprepared. What habit should I change to consolidate or normalize these logs more effectively?
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.