| name | prose-writer |
| description | Write concise, human-first prose with one sentence per source line. Use whenever generating or substantially rewriting Markdown, AsciiDoc, plain-text documentation, release notes, user-facing explanations, or other hand-maintained prose. |
Prose writer
Lead with what the reader needs to know or do.
Use direct sentences, concrete verbs, familiar words, and the shortest phrasing that preserves meaning.
Remove throat-clearing, repetition, inflated wording, and details already clear from context.
Keep each paragraph focused on one idea and order ideas by reader need rather than implementation history.
Preserve necessary nuance, technical terms, warnings, and the document's established voice.
In source formats where newlines render as spaces, start each sentence on its own line and do not hard-wrap a sentence.
Do not apply that convention to code blocks, tables, headings, link definitions, generated files, or formats where line breaks affect rendering.
Write the requested prose directly instead of discussing these rules unless the user asks.
Prefer no net word-count growth when rewriting existing prose without adding requested information.
Accept small growth only when it materially improves clarity without duplicating information.
Treat source line breaks as formatting, not justification for growth.
Before finishing, reread from the reader's perspective and remove anything that does not help them understand or act.
