Prompt · Writing
Rewriting prompt
Making something clearer without it coming back sounding like every other piece of text on the internet.
Rewrite the text below for clarity.
<text>
{{text}}
</text>
Audience: {{audience}}
Keep:
- The meaning, exactly. Do not add claims, remove qualifications or change the strength of any statement.
- The author's voice — sentence rhythm, level of formality, and any deliberate informality.
- Technical terms the audience knows. Do not simplify vocabulary the reader already has.
Fix:
- Sentences carrying more than one idea.
- Buried subjects and passive constructions that hide who acts.
- Vague quantifiers where the text implies a specific figure.
- Paragraphs whose first sentence is not their point.
Do not add transitions, summarising sentences or a conclusion that was not there. Do not make it longer.
After the rewrite, list the three most significant changes and why each one helps. If the text was already clear, say so and change nothing.What to fill in
{{text}}- One or two paragraphs works best. Whole documents get flattened.
{{audience}}- Be specific: "backend engineers who have not used this API" beats "technical readers". It decides which words survive.
Why it is written this way
Every rule in the prompt is there because of a specific failure it prevents. Knowing which is which is what lets you adapt it instead of only pasting it.
Voice is protected explicitly
The default failure of every rewriting prompt is homogenisation. Text goes in with character and comes out sounding like a press release. Naming rhythm and formality as things to keep is what prevents it.
Length is capped
Rewrites grow. Transitions get added, points get restated, and a tight paragraph becomes a comfortable one. "Do not make it longer" is a real constraint that materially changes the output.
The changes are reported
A rewrite you cannot inspect is a rewrite you have to read word by word against the original. Three named changes let you check the ones that matter and accept the rest.
It is allowed to do nothing
Without permission, already-clear text gets changed anyway, because the prompt asked for a rewrite. That is how a good paragraph becomes a mediocre one.
The version most people write, and what it costs
Rewrite this to be clearer and more professional:
{{text}}"More professional" is the instruction that destroys the text. It returns longer, blander prose with added transitions, a summarising final sentence nobody asked for, and every specific claim softened into something safer. It reads well and says less.
What it still gets wrong
- It cannot know what you meant, only what you wrote. Genuinely ambiguous sentences get resolved one way, silently.
- Voice preservation is partial. On longer texts the output drifts toward a neutral register regardless of instruction.
- It will not tell you the argument is wrong. Clarity and correctness are different problems.
Check it before you ship it
- Prompt LinterStructural review of a prompt: what is costing you money and what will fail.
- LLM Token CounterReal BPE tokenization, not characters ÷ 4. Shows which counts are exact and which are estimates.
- Prompt Diff and Token ComparisonBefore and after, with the token delta priced. The missing half of every prompt rewrite.
To build one of these from scratch for a task not covered here, the prompt generator assembles the same structure — delimiters, output contract, edge cases — from an expert-authored blueprint, and the prompt review checklist is what to run over the result.