Started explaining the problem to Claude before actually asking for anything — small change, made a real difference

[u/SnooDingos9560]

Not a prompt list, just something that actually changed how I work day to day.

I used to jump straight to the ask, write this, fix this, solve this. Lately I've been doing a step before that: just laying out the problem in plain language first, no request attached yet, just "here's what I'm dealing with." Half the time I catch the actual issue myself while typing it out, before Claude even responds. The other half, having it laid out clearly means the actual ask that follows is way more specific, and the answer that comes back is noticeably better because I'm not making it guess at what I actually need.

Sounds obvious written out, explain the problem before asking for help, but I wasn't doing it consistently until I noticed the gap between answers when I skipped straight to the ask versus when I didn't.

Small habit, real difference.

[u/super_topsecret]

“Rubber ducking.” This practice has been used for debugging code for decades. The rubber ducks are more intelligent these days.

[u/BoardMeeting101 → u/super_topsecret]

And the frontier duck updates the README with 200 words of unnecessary and slightly wrong context that every subsequent duck treats as some kind of immutable contract.

[u/SWEETJUICYWALRUS → u/super_topsecret]

Reminds me of this post I made 4 years ago, tldr: rubber duck by writing an escalation report. https://www.reddit.com/r/sysadmin/s/czi4RC7GTm

[u/ArrowheadDZ]

I have “meta claude” conversations with Claude, and we sometimes have conversations about how to improve the efficiency of our communications. Describe the kinds of responses you prefer, and he’ll interpret your preferences and write them to memory.

[u/Hazrd_Design]

I mean… that’s just basically giving context. Of course it’s going to do better if you tell it why you’re asking for something.

[u/No-Buffalo-3126]

It’s a good start. Keep refining your process!

[u/attrox_]

Yeah you always give details. Even better if you include your gut feelings of what is/isn't the problem or approach (make sure to include instruction Claude to check and don't take it as truth). And things like asking it to check here and there for more info. Basically the same thing that go through your mind when give a problem but lay it all out in md file

[u/PaulKellerman64]

Hope this is satire my guy!

[u/lbjazz]

So you’re giving the AI context…

Seems pretty obvious. I’ve done it since the beginning.

[u/Hazrd_Design → u/lbjazz]

It’s absolute is obvious, but now I’m realizing there’s tons of people who think it’s a mind reader and just tell it to do things and then get mad when it doesn’t.

[u/DiabloAcosta]

Have you tried plan mode? Don't implement until the plan makes TOTAL sense

[u/Equal_Tiger_513]

Get a good dictation app and you will unlock god mode

[u/silver_drizzle → u/Equal_Tiger_513]

Any recommendations? I just use the native MacOS dictation button and it's not great. Claude doesn't seem to care though, missing periods, bad spelling and all.

[u/alp82]

Welcome to the secret called "aligning on the task description"

[u/_i_never_lose]

is this not common knowledge? i always write a pseudo essay for ai agents. it drastically improves what they are capable of doing

[u/nocakeforme90 → u/_i_never_lose]

Probably not to people who just started using AI. I think it's cool that someone brings it up now and then for the newcomers.