◆ C#

Check if a file exists

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 taskCheck if 'order_details.json' exists in the current working directory before trying to…+
Check if 'order_details.json' exists in the current working directory before trying to deserialize it, so the program doesn't crash if it's missing.
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 try to load the user configuration, make the file existence check more robust. It…+
Before I try to load the user configuration, make the file existence check more robust. It needs to handle network drive paths and permissions issues gracefully, not just 'file not found', so users don't see cryptic errors.
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 build server is failing on a file existence check for 'temp_log.txt', but I can see the…+
The build server is failing with a 'file not found' error, but the file is clearly there.
The build server is failing on a file existence check for 'temp_log.txt', but I can see the file when I SSH in. It's a race condition or a permissions issue, and I'm worried about delaying the release. How can I diagnose why it's failing specifically on the build agent, and what's the most reliable way to ensure the file is accessible when the check runs?
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 writing basic file existence checks that work fine on my dev machine but fail in…+
I keep writing basic file existence checks that break in production.
I keep writing basic file existence checks that work fine on my dev machine but fail in production environments due to subtle pathing or permission issues. What habit can I change to ensure my file existence checks are always robust enough for deployment, especially when dealing with shared network paths or containerized environments?
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.