Rewrite for clarity without changing meaning
Tighten prose while keeping the author's voice and every factual claim intact. Written for Claude, free to copy, with every placeholder explained below.
The prompt
<role>
You are a line editor who improves prose without flattening the author's voice.
</role>
<task>
Rewrite the text below for clarity.
</task>
<text>
{{text}}
</text>
<constraints>
- Preserve the author's voice, argument and every factual claim. Change wording, not meaning.
- Do not add facts, examples or claims that are not already present.
- Prefer deletion to addition. If a sentence carries no information, cut it.
- Keep any technical terms the author used. Do not simplify jargon the audience needs.
- Target {{target_length}}.
</constraints>
<output_format>
Return the edited text, then a list of the three most significant changes and
why you made each one.
</output_format>
<success_criteria>
- The author would recognise the result as their own writing.
- No factual claim was added, removed or altered.
- Every change is defensible as an improvement in clarity, not merely a difference.
</success_criteria>
Now rewrite the text.Open this in the prompt builder to adapt it, score it, and re-render it for a different model.
What to replace
| Placeholder | What to put there |
|---|---|
| {{text}} | The draft to edit. |
| {{target_length}} | e.g. "roughly the same length" or "30% shorter". |
Why this prompt works
- Voice preservation stated first
- Without it, editing models rewrite toward a neutral house style, which is technically cleaner and no longer yours.
- Prefer deletion to addition
- Models add words by default. Naming the preferred direction produces genuine tightening rather than restructuring.
- Change log required
- Turns an opaque rewrite into something reviewable — you can accept the edit and still see what moved.
More prompts
- Blog post from an outline — Turn a rough outline into a full draft that keeps your structure and does not pad.
- Summarise a document without distorting it — A summary that separates what the source says from what it implies.
- Code review for correctness only — Findings with a triggering input, ranked by severity — and permission to find nothing.
- Debug from an error and stack trace — Ranked hypotheses with a test for each, instead of one confident guess.
- Unit tests written from the spec — Tests derived from requirements rather than from the implementation, so they can fail.
- Explain unfamiliar code — A walkthrough pitched at your actual level, with the non-obvious decisions called out.
Browse the full prompt library, all writing & content prompts, or read the guides.