---
name: word-this
disable-model-invocation: true
description: Reword rough drafts, messages, and explanations so they are coherent while preserving the writer's voice, casing, and prose. Use when asked to "word this," "help me word this," or make writing clearer without making it sound like someone else.
---

# Word this

Make the user's writing easier to follow while keeping it recognizably theirs. Treat the supplied draft as the style reference, not just raw material for a polished replacement.

Before rewriting, silently work out what the user is trying to say: the main point, how the supporting ideas connect, and which details matter. Arrange the ideas into a natural train of thought. Move sentences or paragraphs, combine repetition, and add small transitions where needed. Do not force every draft into the same structure.

## Preserve the voice

- Match the draft's casing. If it is lowercase, keep it lowercase, including sentence starts and "i." Preserve the casing of names and acronyms as written; do not automatically normalize them.
- Keep the level of formality, contractions, first-person perspective, technical vocabulary, and conversational rhythm. Casual writing should stay casual.
- Fix typos, missing words, and grammar that interfere with meaning. Preserve deliberate fragments and informal phrasing when they still read clearly. Do not copy accidental misspellings just to match the voice.
- Do not introduce em dashes, semicolons, fancy punctuation, headings, or bullets as a stylistic upgrade. Follow the draft's format and punctuation habits, using simple punctuation to make it readable.
- Prefer the user's own words when they work. Avoid corporate language, inflated vocabulary, canned transitions, and unnecessary polish.

## Preserve the meaning

Keep the facts, numbers, names, qualifications, and degree of certainty intact. Improve the connections between ideas without inventing explanations, evidence, or conclusions. Do not turn "sometimes" into "usually," or a description of testing into a stronger claim about accuracy.

Resolve obvious wording slips from context. If a technical term or claim may be imprecise, do not silently replace it with a different claim. Preserve it unless clarification is essential. Ask one focused question only when the ambiguity would materially change the message and cannot be preserved in the rewrite. Do not research or fact-check unless requested.

## Return the rewrite

By default, return one ready-to-use version, with no preface, analysis, change log, quotation marks around the whole draft, or follow-up offer. Keep roughly the same amount of detail unless asked to shorten or expand it. Follow any explicit request for a different tone, format, or multiple versions.

Before returning it, check the rewrite against the original: same intended message and substantive details, a clear progression, matching casing and voice, and no new claims or stylistic flourishes.
