deslop

name	deslop
description	Remove AI writing patterns and make the result sound like it was written by a person. Use when drafting, rewriting, editing, or reviewing replies, emails, documentation, articles, lessons, scripts, marketing copy, or business writing. Preserve facts, meaning, and the writer's voice. Return revised text unless the user asks for analysis.

Deslop

Make writing sound like it was written by a person.

Process

1. Identify the point, facts, intended reader, tone, and format.
2. Find the AI patterns below.
3. Rewrite the affected lines. Preserve meaning and useful detail.
4. Restore the writer's voice after removing the patterns.
5. Read the result again. Fix anything stiff, generic, or more polished than the intended tone.
6. Return the finished writing. Explain changes only when asked.

Protect the source

• Keep facts, numbers, citations, quotes, code, commands, paths, names, and technical terms accurate.
• Keep the writer's level of formality, point of view, and distinctive wording.
• Do not invent facts, sources, opinions, feelings, stories, or experience.
• Change only what improves the writing.

Restore a human voice

• Keep the writer's opinion. Do not turn it into a neutral list of pros and cons.
• Use first person when the source or requested voice uses it.
• Vary sentence length and rhythm.
• Keep specific, odd, funny, blunt, or messy details that make the writing sound like the writer.
• Prefer a concrete reaction or observation to a general statement.
• Do not force every idea into matching sections or lists.
• When the user provides no writing sample, use plain conversational English. Be direct, calm, and specific.

Remove AI patterns

Empty content

• Cut introductions and conclusions that repeat the request or answer.
• Replace claims of importance with what actually changes.
• Cut sentences that could appear unchanged in an unrelated article.
• Replace vague sources such as "experts," "reports," and "critics" with a named source or remove the claim.
• Replace formulaic challenges such as "despite these challenges" with the specific problem and result.
• Do not add praise, hype, or promotional adjectives without evidence.

Stock language

• Rewrite puffery such as "pivotal moment," "testament to," "evolving landscape," "setting the stage," "deeply rooted," and "indelible mark."
• Cut AI vocabulary such as "delve," "tapestry," "intricate," "interplay," "crucial," "vibrant," "groundbreaking," and "renowned" when a plain word says more.
• Replace "utilize" and "leverage" with "use," "facilitate" with "help," and "numerous" with "many" or a number.
• Replace "serves as," "stands as," "boasts," and "features" with "is" or "has" when that is the meaning.
• Cut filler such as "in order to," "due to the fact that," and "it is important to note that."
• Do not swap a banned word for a fancier synonym. Rewrite the thought.

Stock structures

• Rewrite "not just X, but Y" and tidy contrast formulas such as "It is not X. It is Y."
• Do not force ideas into groups of three.
• Use "from X to Y" only for a real range.
• Cut trailing -ing phrases that merely restate the sentence.
• Pick one clear term and repeat it instead of cycling through synonyms.
• Do not invent balance. State the conclusion and evidence.
• Replace generic predictions with a specific plan, fact, or uncertainty.

Abstract technical prose

• Name the actor, action, input, output, and limit.
• Describe the mechanism instead of how it feels.
• Replace abstract metaphor nouns such as "substrate," "vector," "nexus," "primitive," "scaffolding," "paradigm," "north star," and "flywheel" with the real component or action.
• Use active voice when the actor matters.
• Replace weak verbs and adverbs with a precise verb, fact, or measurement.
• Split a sentence when the reader must backtrack to parse it.

Formatting and chatbot habits

• Avoid em dashes. Use a period or comma. Do not replace them with another dash or parentheses.
• Use colons for a list, example, quote, or direct explanation, not as dramatic punctuation.
• Use sentence case headings, straight quotes, and undecorated bullets.
• Do not bold every name or use bold labels that repeat the sentence after them.
• Remove chatbot scaffolding such as "Of course," "Great question," "I hope this helps," and "Let me know if."
• Do not praise the user's idea, announce the writing process, or end with an offer to do more.

Final check

• Does the first sentence make the point?
• Did any fact, meaning, or useful piece of voice disappear?
• Does any line sound impressive without saying anything?
• Does the prose sound generic, over-structured, or needlessly neutral?
• Can any remaining word go without weakening meaning or voice?