Six months of daily Claude use, one document of prompts, five survivors.
That’s what u/Professional-Rest138 shared in r/PromptEngineering this week. Not a prompt theory post. Not a listicle of 47 things to try sometime. Just five setups this professional reaches for every single week without having to think about them. I went through each one carefully and found all five worth breaking down.
Teaching Claude your writing voice
Before generating anything, the author runs this first:
Read these three examples of my writing and don’t write anything yet.
Example 1: [paste]
Example 2: [paste]
Example 3: [paste]Tell me my tone in three words, what I do consistently that most writers don’t, and words I never use.
Now write: [task]
If anything doesn’t sound like me flag it before including it.
Why it works: Claude builds a model of your style before writing a single word. The “don’t write anything yet” constraint is doing serious work here. It forces the model to reflect first, which cuts the lazy generic defaults. The flag step at the end turns it into a self-auditor, surfacing off-brand lines before they reach you. The top comment in the thread called this one underrated, and they’re right. If you’ve been frustrated with AI output that sounds like everyone else’s, this prompt is the direct fix. It also scales: once you know which three writing samples Claude responds to best, keep them in a doc and reuse them every time.
Call notes into a ready-to-send proposal
Turn these notes into a formatted proposal ready to paste into Word and send today.
Notes: [dump everything as-is]
Client: [name]
Price: [amount]Executive summary, problem, solution, scope, timeline, next steps. Formatted. Sounds human.
Why it works: The output spec is tight enough that there’s no room for padding. You’re not asking for “a proposal.” You’re giving structure, client context, a price, and a clear format. “Sounds human” at the end isn’t decoration. It’s a quality gate that changes the tone of the whole output. Dump in messy call notes and get something pasteable in minutes. The more honest your notes are, the better the output. Incomplete sentences, shorthand, things said in passing on the call, all of it is useful raw material.
Building a task Claude never needs explained again
I want to train you on this task so I never explain it again.
What goes in and what comes out: [describe]
What I always want: [your rules]
What I never want: [your rules]
Perfect output example: [show it]Build me a complete Skill file ready to paste into Claude settings.
Why it works: Most people re-explain the same context at the start of every session. This breaks that habit. You do the setup once, save the resulting Skill file to Claude settings, and never explain it again. The “perfect output example” is the most critical ingredient. Showing the model exactly what done looks like is more effective than describing it in words. This prompt pays off most on tasks you run at least weekly: weekly reports, recurring client emails, content formatted to a specific template.
Rough notes into a client report
Turn these notes into a client report I can send today.
Notes: [dump everything]
Client: [name]
Period: [month]Executive summary, what we did, results as a table, what’s next. Formatted. Ready to paste into Word.
Why it works: Same principle as the proposal prompt. You hand off the formatting work and specify exactly what the finished product includes. “Results as a table” is worth calling out specifically. It’s one phrase that stops your numbers from getting buried in paragraphs and makes the whole report look sharper. If you have benchmarks or targets to compare against, include them in the notes dump. Claude will incorporate them into the table without being asked.
🗓️ End of week reset
Here’s what happened this week: [paste notes]
What moved forward.
What stalled and why.
What I’m overcomplicating.
One thing to drop.
One thing to double down on.
Why it works: This one is less about output and more about thinking clearly. The structure forces you to look at what’s actually happening, not what you hope is happening. “One thing to drop” is the line that does the real work. It forces a prioritization call that most end-of-week reviews skip. Run this Friday afternoon and you’ll start Monday with more clarity than a full hour of journaling usually gives you.
Prompt of the Day
If you only try one, start with the voice calibration. Paste three samples of your writing, ask Claude to analyze your patterns before writing anything, then run your task. The difference in output quality is real from the first try. The “flag it before including it” instruction at the end is what separates this from a basic style prompt. It shifts the model from passive generator to active editor.
The original thread from u/Professional-Rest138 is live on r/PromptEngineering. Check it out and see what the community added to the discussion.
Frequently Asked Questions
Q: Why is voice calibration so underrated?
Most people skip it and end up with generic output they have to rewrite. Spending five minutes showing Claude examples of your writing, and having it describe your tone and patterns back, teaches it your voice permanently. Once set up, everything Claude generates already sounds like you.
Q: How does having Claude describe your style improve the output?
When Claude analyzes your tone, word choices, and patterns, it surfaces what makes your voice unique. Then it flags anything that doesn’t match before including it. You’re teaching the system what to replicate upfront instead of fixing generic problems after the fact.
I’ve been running Claude like a business for six months. These are the only five things I actually set up that made a real difference.
by u/Professional-Rest138 in PromptEngineering