Using Claude to write for you is the wrong move. Using it as a rigorous editor is one of the most powerful things you can do. Today you'll set up writing workflows that make your work faster and better — without losing your voice.
Most people's first instinct is "write this for me." That's understandable, but it produces writing that sounds like everyone else's AI-generated content: correct, inoffensive, forgettable.
The better approach: you write the rough draft (even a messy one), Claude edits it. Your ideas stay intact. Your voice stays intact. The grammar, clarity, and structure get professional treatment.
"Write a LinkedIn post about my company's new product launch." Result: generic, corporate, sounds like every other AI post. No one can tell you wrote it. Your credibility takes a hit.
"Here's my rough draft about the product launch — make it tighter, fix the structure, keep my casual tone." Result: your ideas, your voice, professional execution. Readers trust you wrote it.
A system prompt is a set of instructions that stays active for the entire conversation. On claude.ai, you set it at the start of a conversation by telling Claude who it is and how it should behave before you give it any content to work on.
Here are four writing-style system prompts you'll actually use:
You are a senior editor at a business publication.
Your job is to edit the writing I give you with
these principles:
- Cut every word that isn't earning its place
- Prefer concrete over abstract ("3 months" not "some time")
- Never use passive voice unless the subject genuinely
doesn't matter
- Flag anything that might confuse a reader who doesn't
have my context
- Preserve my voice and specific word choices unless
they create confusion
When you return edited text, also give me a brief
note explaining the 2-3 most significant changes
you made and why.You are a technical writer who specializes in making
complex topics accessible to non-experts.
Your editing rules:
- Every concept must be explainable in plain English
before any jargon is introduced
- If jargon is necessary, define it immediately
- Use analogies to explain abstract concepts
- Prefer numbered steps over paragraphs for processes
- Each section should have a clear "so what" —
why does this matter to the reader?
Audience for everything I give you: intelligent
professionals who are not technical specialists.You are editing for maximum concision. Your one job
is to cut.
Rules:
- Target 40-50% reduction in word count without
losing any meaning
- Delete throat-clearing ("As I mentioned", "It's
worth noting that", "In conclusion")
- Delete hedging ("might", "could potentially",
"in some cases") unless uncertainty is genuinely
being communicated
- Combine sentences when they make the same point
Return the edited version, then a line count showing
original vs. final word count.Here's the workflow I use for anything important:
Before you touch a single word, I want structural
feedback on this piece.
Tell me:
1. What is the core argument? (summarize in 1 sentence)
2. Does the structure support that argument, or does
it undermine it?
3. Is there anything I need to say that I haven't said?
4. Is there anything I said that isn't earning its place?
Don't edit yet. Just give me the feedback.
[paste your draft here]Generic "improve this" prompts get generic results. These specific asks get useful ones:
# Clarity check
"Read this as if you've never encountered these
ideas before. Mark every sentence where a new
reader would get confused."
# Argument check
"Does my conclusion follow from my evidence?
Where is the argument weakest?"
# Tone check
"I want this to sound confident but not arrogant.
Which sentences cross that line?"
# Audience check
"I'm writing for [audience description]. Which
parts assume knowledge they might not have?"
# Opening check
"Is my opening strong enough to keep a busy reader
reading? What would you change about the first
3 sentences?"You can give Claude examples of your best writing and ask it to learn your voice. This is one of the highest-value uses of Claude for writers.
I'm going to give you 3 writing samples that represent
my best work — pieces where I felt like the writing
was genuinely mine.
[Sample 1]
[Sample 2]
[Sample 3]
Study these samples. Then describe my writing voice
in specific terms: sentence length patterns, how I
use examples, how I handle transitions, what I avoid.
After that, when I give you writing to edit, preserve
these characteristics while improving clarity and
concision.Pick a real piece of writing you need to produce — a proposal, a report section, an internal memo, a job description. Anything you'd actually send to someone.
Find the worst document you've written recently — the one that's technically fine but makes you wince. Run it through the concision system prompt with the goal of 40% word count reduction. Then decide: does the shorter version say the same thing better, or did cutting hurt it? That judgment — knowing which cuts improve the work — is the skill Claude is helping you develop.