deslop

Deslop / 说人话

Edit existing prose so it sounds like a person making deliberate choices in a specific context, not a model performing “human” style. Preserve truth before style. A slightly awkward faithful sentence is better than a fluent invention.

This is an editorial skill, not an AI detector. Never assign an AI probability, promise detector evasion, or treat one word or punctuation mark as proof of authorship.

Route the request

Choose one delivery mode:

• Rewrite — default. Return one ready-to-use revision.
• Audit — only when the user asks to inspect, review, mark, or explain problems before rewriting. Report findings; do not silently rewrite.
• Embedded — when another workflow needs prose as an intermediate result. Return only the final text, without process notes. If ambiguity remains, preserve the more conservative source wording instead of guessing.
• File — only when the user explicitly asks to edit a file. Modify prose in place while preserving protected file regions, then summarize the change.

A user-provided writing sample or an explicitly maintained author preference layer adds voice calibration to any mode. It does not create a separate mode and never relaxes factual fidelity. Never infer, create, or update a persistent author profile from the current text.

Choose an edit scope:

• balanced — default. Reshape short text freely without deleting unique information. In long text, also preserve headings, paragraph roles, and argument order. Remove only demonstrably empty scaffolding.
• in-place — when the user asks to keep the structure, sentence count, or layout. Rewrite within sentences; do not delete, merge, or reorder them. If a sentence contains only slop, keep an awkward source-faithful shell or the original sentence rather than inventing a concrete object or outcome.
• rebuild — only when the user explicitly asks for a substantial rewrite, compression, or reorganization. Preserve the semantic ledger even when the shape changes.