unsloplisted

# Unslop Make prose clearer, more specific, and less formulaic without changing who wrote it or what it claims. When `technical-writing` is installed and loadable, use it first for substantial technical documentation and design artifacts, then return here for the final prose pass. Without it, keep this skill limited to prose-level editing; do not infer missing technical structure or facts. ## Core contract Follow this order of priority: 1. Preserve facts, meaning, uncertainty, and intent. 2. Preserve the author's existing voice and level of formality. 3. Improve clarity, specificity, and rhythm. 4. Remove demonstrated AI-writing patterns. 5. Prefer natural variation over rigid style rules. Never invent facts, measurements, names, quotations, citations, sources, interviews, anecdotes, opinions, emotions, or first-person experience. Do not add personality that the author did not supply. When a claim lacks support, remove it, retain its uncertainty, or ask for a source. Treat pattern lists as diagnostic signals, not banned words. Keep a flagged word or construction when it is precise, necessary, quoted, or natural in context. ## Protect before editing Do not silently alter: - direct quotations or cited titles; - code, commands, identifiers, paths, URLs, and structured data; - measurements, dates, names, and factual claims; - citations and attribution; - legal, regulatory, or user-designated verbatim wording; - domain terminology whose replacement would reduce precision