Writing & Editing with Claude

Writing is one of Claude's strongest skills — but the quality of what you get depends heavily on how you ask. The difference between a generic output and something genuinely useful is usually in the specificity of your instructions about tone, audience, format, and purpose.

First Drafts vs Rewrites

These are different tasks that require different prompting approaches:

Tone and Style Instructions That Work

Tone instructions are the most important part of a writing prompt. Vague instructions produce generic prose; specific instructions produce useful output:

The fastest way to get the right tone: give Claude an example of writing you like. "Write this in the style of [paste example]" is more reliable than describing the style in words.

Editing Without Losing Your Voice

When asking Claude to edit existing writing, the risk is that it smooths out your voice into generic AI-sounding prose. Prevent this:

• Be explicit about what to preserve: "Edit for clarity and grammar — do not change my sentence structure, word choices, or jokes. Keep my voice."
• Ask for tracked changes, not a rewrite: "Show me only what you'd suggest changing — don't rewrite the whole thing." Claude can respond with inline suggestions.
• Use iterative editing: Instead of "edit my whole essay", work section by section. This lets you accept or reject each change before moving on.
• Provide your style as context: Paste a previous piece you're happy with at the start of your prompt — "Here's a piece I wrote previously that has the voice I want to maintain. Edit the new draft to match."

Long-Form Writing: Maintaining Coherence

For long-form content (reports, articles, proposals), Claude performs best when you manage the structure explicitly:

• Write an outline first: Ask Claude to generate an outline, review and refine it, then ask Claude to write each section based on the approved outline. This prevents structural drift.
• Brief each section: Rather than "write a 2,000-word article about X", feed Claude one section at a time with context about what came before: "Here's the intro and Section 1. Now write Section 2, which should [purpose of section 2]."
• Use Projects for multi-session work: If you're writing something over multiple sessions, use a Claude Project. Upload existing drafts to the knowledge base so Claude has continuity between sessions.

Examples vs Descriptions

When you want a specific style or format, showing is almost always better than describing:

• "Write an email like this: [paste example]" beats "Write a concise, professional email with a clear ask."
• "Format the output like this: [paste desired format]" beats trying to describe your desired structure in words.
• For tone: paste 2–3 sentences from something you've written or admire, then say "match this tone."

Checklist: Do You Understand This?

• First drafts need: purpose, audience, tone, key points, and length — all specified upfront
• Rewrites need: explicit instruction on what to change and what to preserve
• Specific tone instructions ("confident and direct") outperform vague ones ("professional")
• Giving Claude an example of your voice is more reliable than describing it in words
• Long-form writing works best with an explicit outline and section-by-section generation
• Use Projects for multi-session writing work — upload your drafts to the knowledge base for continuity