Writing

Editing

Tighten, restructure, and proof existing drafts.

Knowledge cards
Knowledge card
Cut It to Length Without Losing the Point
An editing pattern for cutting a piece to a target length where you tell Claude the exact target and, crucially, what must survive the cut — the core point, the call to action, the key example — so it trims aggressively without gutting the message.
L2 · Context engineering
Workflow
Edit for One Problem Per Pass
An editing workflow that runs the draft through Claude one concern at a time — structure, then clarity, then tone, then proofreading — instead of asking it to 'make this better' in a single sweep. Each pass has exactly one job.
L2 · Context engineering
Knowledge card
Get a Critique Before You Ask for an Edit
An editing pattern where you first ask Claude to critique your draft — name its weak spots, unclear passages, and unsupported claims — before you ask it to rewrite anything, so the edit targets real problems instead of rewriting on instinct.
L2 · Context engineering
Knowledge card
Make Claude Edit Without Erasing Your Voice
An editing pattern where you explicitly constrain Claude to fix specific problems while preserving your voice — your rhythm, word choices, and quirks — instead of letting an open 'improve this' smooth the draft into generic prose.
L2 · Context engineering
Claude for editing

Separate the kinds of edit

Editing well means not doing everything at once. Ask Claude for one kind of change at a time — structure and argument, then clarity and concision, then tone and word choice — so you can judge each on its own terms. A single 'make this better' returns a wholesale rewrite you have to re-read entirely, with no clear sense of what changed. Passes keep you in control: you accept the structural fixes, weigh the clarity edits, and protect the voice, deliberately rather than by accident.

Tell it what to leave alone

Claude edits faithfully when you tell it the boundaries. Name what to preserve — your voice, a deliberate phrasing, the precise meaning of a technical sentence — so it tightens without flattening or changing what you meant. Ask it to flag or explain notable changes rather than silently rewriting, so nothing slips past you. Good editing is restraint as much as improvement, and Claude follows that instruction well when you give it explicitly.

Frequently asked
How do I edit with Claude effectively?

Work in separate passes — structure, then clarity, then tone — rather than one blanket 'improve this'. Passes keep you in control of what changes and why.

How do I keep my voice when Claude edits?

Tell it explicitly what to preserve — your voice, specific phrasings, the meaning of technical sentences — and ask it to flag notable changes rather than rewriting silently.

Why does Claude over-edit my drafts?

Usually because the instruction was open-ended. Naming the boundaries and the single kind of edit you want keeps it tightening rather than rewriting wholesale.