The short version: Claude is a better editor of your own writing than you are, because it doesn't fall in love with the sentence you worked hardest on. The trick is giving it narrow, specific editing jobs instead of one vague "make this better" prompt, and treating every suggestion it gives you as a draft to argue with, not an order to follow.
I've spent five years rebuilding a business in public, which means I've written more blog posts, emails and LinkedIn updates than I'd like to count. Most of them went through Claude at some point. Not for the first draft, I still write those myself, but for the bit I'm worst at: cutting my own darlings and spotting where I've gone soft.
Why editing is the job Claude is good at
Everyone wants an AI to write the thing for them. Fine, but the writing it produces for you is usually bland, and you know it the moment you read it back. Editing is different. Give Claude a piece of writing that already has your voice in it and ask it to find specific faults, and it's quietly brilliant, because it has no ego attached to the draft. It will tell you your third paragraph repeats your first without flinching, something a friend reading it for you often won't bother to say.
The uncomfortable bit nobody wants to hear: if you ask Claude to "edit this" with no further instruction, you'll get a smoothed-out, slightly corporate version of your writing that reads worse than your original, not better. It sands off the edges that made it sound like you. The fix isn't avoiding Claude for editing, it's being brutally specific about what kind of edit you want, one pass at a time.
The one-job-at-a-time rule
Don't ask for everything at once. A single prompt that says "check grammar, tighten it, make it punchier, check it flows, and make sure it's SEO-friendly" will get you a muddled result because Claude is trying to satisfy five goals in one answer. Instead, run separate passes:
- Pass 1: structure and argument
- Pass 2: cutting length
- Pass 3: sentence-level rhythm
- Pass 4: the opening and closing lines specifically
- Pass 5: a final "what would a sceptical reader push back on" check
Five short prompts beat one long one, every time. It also means you can accept pass 2's cuts without being forced to accept pass 4's suggested ending, which you might hate.
Worked example: tightening a 900-word blog draft
Say you run a small accountancy practice and you've written a 900-word blog post for your website about why small businesses miss tax deadlines. Your first draft is honest but baggy, three paragraphs in before you make your actual point. Here's how a real editing pass with Claude would look.
Prompt 1 (structure): "Here is a 900-word draft blog post. Read it and tell me, in bullet points, where the main argument starts, which paragraphs could be cut entirely without losing meaning, and whether the order of points makes logical sense. Do not rewrite anything yet, just diagnose."
Claude might come back and tell you the real argument starts in paragraph four, paragraphs one to three are throat-clearing, and your strongest point, about HMRC's penalty structure, is buried near the end when it should open the piece. That alone, before a single word is rewritten, is worth the whole exercise.
Prompt 2 (cutting): "Cut this to 600 words without losing any of the specific numbers or examples. Show me what you removed in a separate list so I can check I'm not losing anything important."
This is the step most people skip, asking Claude to show its cuts. Without that, you can't tell if it quietly deleted the one concrete detail that made the post worth reading.
Prompt 3 (sentence rhythm): "Go through this paragraph by paragraph. Flag any sentence over 30 words and suggest a shorter alternative. Flag any sentence that starts with 'It is' or 'There are' and rewrite it to start with a stronger subject."
That one prompt alone will usually fix 60 to 70 percent of the flabbiness in a typical first draft, because weak openers and overlong sentences are the two most common faults in business writing.
Prompts that catch what you can't see in your own work
These are the ones I'd keep pinned somewhere, because they catch blind spots specific to editing your own writing rather than someone else's:
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
- "Read this as if you've never heard of me or my business before. What questions does it leave unanswered?"
- "List every sentence in this piece that could apply to literally any business in any industry. I want to cut generic sentences."
- "Which paragraph would a tired reader stop reading at, and why?"
- "Find three places where I've told the reader something instead of showing them with a number, example or specific detail."
- "Read the first and last paragraph only. Do they feel like they belong to the same piece of writing?"
That third one is the most useful prompt I've found for any long-form writing, blog posts, long emails, even LinkedIn posts. Writers rarely know where their own piece goes slack. Claude will tell you flatly, which stings slightly and is exactly why it's useful.
Editing for voice, not just correctness
Most editing advice online focuses on grammar and clarity. Fine, but that's the easy 20 percent. The hard 80 percent is keeping your voice intact while tightening the writing, and this is where most people get Claude editing wrong. If you paste in a paragraph and say "fix this," Claude defaults to a neutral, slightly formal tone that erases whatever made the writing sound like a person wrote it.
The fix is to give Claude a short voice brief once, and reuse it. Something like: "My writing style is direct, uses short sentences for emphasis, avoids corporate language, and includes specific numbers rather than vague claims. When you edit my writing, preserve this style. Flag anywhere the edit makes it sound more generic, don't just apply it." Paste that at the start of every editing session, or better, build it into a Claude skill so you're not retyping it every time. If you're doing this kind of editing daily, it's worth looking at how skill-creator handles repeatable instructions like this one, because a saved skill beats pasting the same brief into every new chat.
A step-by-step editing routine you can reuse
Here's the routine I'd set up if I were starting from scratch:
- Write the full first draft yourself, badly if needed. Don't edit while drafting.
- Run the structure diagnosis prompt. Fix structure problems manually before anything else.
- Run the cutting prompt with a target word count 30 to 40 percent lower than your draft.
- Run the sentence rhythm prompt on the sections you cut least from, they're usually the ones hiding the weakest writing.
- Read the whole thing aloud once. This catches rhythm problems no prompt will find.
- Run the "generic sentence" prompt last, right before publishing, as a final filter.
Six steps, maybe 20 minutes for a 1,000-word post once you've done it a few times. That's considerably less time than most people spend rereading their own draft seven times and still missing the weak paragraph in the middle.
Where this goes wrong
The mistake I see most is people accepting every suggested edit wholesale, pasting Claude's rewrite over their own paragraph without reading it critically. That defeats the purpose. Claude's job in this process is to point at problems and offer one possible fix, not to become the author. If a suggested rewrite sounds nothing like you, reject it and ask for a second option, or fix it yourself using Claude's diagnosis as the starting point.
The other mistake is using Claude to edit writing you haven't drafted yet, hoping the tool will paper over a weak first attempt. It won't. Editing prompts sharpen an argument that already exists, they don't invent one. If your first draft has no real point, no amount of prompting will fix that, you need to think harder about what you're trying to say before you open Claude at all.
Frequently asked questions
What's the best single Claude prompt for editing my own writing?
There isn't one best prompt, there's one best approach: ask for a structure diagnosis first, separate from any rewriting, so you fix the bones of the piece before worrying about sentences. "Tell me where the argument really starts and what could be cut entirely" catches more problems than any polish prompt.
Will Claude make my writing sound less like me?
It can, if you give it a vague instruction like "edit this." Give it a short written brief about your actual style, direct, short sentences, specific numbers, no corporate language, and ask it to flag anywhere its edit makes the writing sound more generic rather than just applying the change automatically.
How many editing passes should I run on one piece?
Four or five separate passes beats one long combined prompt. Structure, then cutting length, then sentence rhythm, then the opening and closing lines specifically, then a final check for generic sentences right before you publish.
Can Claude fix a weak first draft?
No, and that's worth knowing before you rely on it. Editing prompts sharpen an argument and tighten sentences, they don't invent a point you haven't made yet. If the draft has nothing to say, fix that first, then bring Claude in for the edit.
Run a business, a brand or a blog? I feature tools, products and expert guest posts for an audience of 15,000. See how it works
