◆ C#

Design and generate reports

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 taskDesign a new report for the sales team that shows monthly revenue by product line, with a…+
Design a new report for the sales team that shows monthly revenue by product line, with a year-over-year comparison, and export it to Excel.
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 finalize this sales revenue report, make sure it's easy for the sales director to spot…+
Before I finalize this sales revenue report, make sure it's easy for the sales director to spot trends and outliers, allows filtering by region, and includes a summary chart that visualizes the year-over-year growth for the top five product lines.
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 sales director just asked for a breakdown of revenue by new versus existing customers for…+
The sales director just asked for a breakdown of revenue by new versus existing customers, but that data isn't directly in our CRM.
The sales director just asked for a breakdown of revenue by new versus existing customers for the Q3 review, but that data isn't directly in our CRM and would require joining multiple tables and some complex logic to infer. I'm afraid of telling him it's impossible, but I also don't want to promise something I can't deliver by Friday. What's the best way to approach this request, and is there a common pattern for identifying new vs. existing customers from transactional data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often struggle to translate vague business questions into precise, actionable report designs,…+
I often struggle to translate vague business questions into precise, actionable report designs.
I often struggle to translate vague business questions into precise, actionable report designs, leading to multiple revisions and wasted effort. I need to get better at clarifying requirements upfront. What habit should I change to ensure I fully understand the business need and the underlying data before I even start designing a new report?
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.