What Did Claude Write That You Couldn’t Send?
HubAiPrompt
5 minutes ago
Think of the last time Claude gave you something you couldn’t send to a client.
Not wrong, just not sendable. Too stiff, too long, too eager, or it sounded like every other AI email.
What happened next
You fixed it by hand. It probably took ten minutes.
It probably happened again this week.
That’s the task worth fixing.
A quick fix you can use today
For the most common version of this problem, add two things to your prompt:
A short sample of your own writing, a few sentences from an email you were happy with.
One line: “Match this voice. No stock openers, no corporate phrases.”
Claude copies what you show it better than what you describe. “Make it sound more like me” gives it nothing to copy. A real sample does.
If it’s still off
Don’t reword the whole prompt. Find the part that bothered you and add it as a rule.
If it opened with “I hope this finds you well,” ban that line. If it ran too long, add a word limit. Each fix stays in the prompt, so the same problem doesn’t come back next week.
Now tell me which task it is
Hit reply with three lines:
Task: what you keep asking Claude for
For: who it goes to
What’s wrong: why you can’t send it as-is
Here’s an example:
Task: weekly client update
For: clients who want a short progress note
What’s wrong: it sounds like a press release
What happens to your reply
The three most specific replies get built into free templates next week, right here.
The sharper your “what’s wrong” line, the better the template. “It’s too formal” is a start. “It uses words I’d never say out loud” is better.
Top comments (0)