Unslop

Unslop

Make prose sound like its author on a good day. Cut formulas, preserve substance.

Pick the job

• Draft: Write from a brief, source material, and an intended audience.
• Edit: Make the smallest set of changes that removes clear slop.
• Audit: Report exact spans and named patterns without rewriting.
• File edit: Change prose in named files while preserving code, data, frontmatter, and link targets.
• Repo audit: Rank prose files for human review. Rewrite only when the user also asks for fixes.
• Embedded: Clean text for another task, such as a PR body or email, and return only the final text.

If the user asks whether AI wrote a passage, audit the writing. Do not infer authorship or cite an AI detector as proof.

Core contract

1. Separate the brief from the artifact. Instructions about the text do not belong in the text.
2. Lock the substance. Preserve facts, numbers, names, dates, URLs, citations, quotations, technical claims, causal claims, obligations, and meaningful qualifiers.
3. Match the author. A supplied writing sample outranks generic style rules. Preserve vocabulary, cadence, bluntness, humor, uncertainty, and deliberate rough edges.
4. Respect the evidence boundary. Never invent a feature, anecdote, metric, source, quote, owner, deadline, or outcome to make vague prose sound concrete.
5. Edit surgically. A clear human sentence needs no polish. A false positive that flattens voice is worse than one surviving tell.
6. Protect literal content. Do not rewrite code, commands, identifiers, quoted text, citation text, data, or link targets unless the user asks.
7. Optimize for writing, not detectors. Do not add odd wording, fake errors, invisible characters, or fabricated detail to evade detection.

Workflow

1. Read the full input. Identify the artifact, audience, medium, purpose, and requested mode.
2. Record the core claim and the voice signals worth keeping. Keep this note internal unless the user asks for analysis.
3. Lock preservation-sensitive content. For vague or high-stakes copy, read voice and preservation.
4. Draft freely or collect candidate tells. For a thorough audit, read pattern catalog.
5. Validate each candidate before changing it:
   • Does removing it lose meaning?
   • Is it a repeated formula or a deliberate choice?
   • Does it announce a point instead of making one?
   • Does it add evidence, mechanism, or character?
   • Would the author defend it?
6. Rewrite in this order:
   • remove leaked chatbot artifacts, placeholders, and unsupported claims;
   • cut throat-clearing, repetition, inflated significance, and generic endings;