Back to Details

unslop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Unslop

Unslop

Edit text to remove AI patterns and add human voice.
编辑文本以去除AI生成模式，赋予人文语气。

Process

操作流程

  1. Scan for the patterns below.
  2. Rewrite. Preserve meaning, match intended tone.
  3. Add soul (see next section).
  4. Self-audit: "What makes this obviously AI generated?" Fix remaining tells.
  1. 扫描以下列出的AI生成模式。
  2. 重写文本。保留原意，匹配预期语气。
  3. 注入“灵魂”（见下一节）。
  4. 自我审核：“哪些地方明显是AI生成的？”修正剩余的AI痕迹。

Adding soul

注入人文灵魂

Removing patterns is half the job. Sterile, voiceless writing is just as obvious.
  • Have opinions. React to facts instead of neutrally listing pros and cons.
  • Vary rhythm. Short sentences. Then longer ones that take their time. Mix it up.
  • Acknowledge complexity. "Impressive but also kind of unsettling" beats "impressive."
  • Use "I" when it fits. First person isn't unprofessional.
  • Let some mess in. Perfect structure feels algorithmic.
  • Be specific. Not "this is concerning" but "there's something unsettling about agents churning away at 3am."
去除模式只是完成了一半工作。刻板、缺乏个性的文本同样会暴露AI生成的痕迹。
  • 表达观点：针对事实做出回应，而非中立地罗列优缺点。
  • 变换节奏：先用短句，再用从容的长句，交错使用。
  • 承认复杂性：“令人印象深刻但也有点不安”比“令人印象深刻”更真实。
  • 适当使用第一人称：第一人称并非不专业。
  • 保留些许“瑕疵”：完美的结构会显得像算法生成的。
  • 具体化表达：不要说“这令人担忧”，而要说“Agent在凌晨3点不停运转的场景，总让人觉得有点不安。”

Patterns to detect and fix

需要识别并修正的AI生成模式

Content

内容层面

  1. Significance inflation. "pivotal moment", "testament to", "evolving landscape", "setting the stage for", "indelible mark", "deeply rooted". Cut puffery, state what happened.
  2. Notability name-dropping. Listing media outlets without context. Pick one, say what was said.
  3. Superficial -ing phrases. "highlighting...", "ensuring...", "reflecting...", "showcasing...", "fostering...". Delete or expand with real sources.
  4. Promotional language. "nestled", "vibrant", "breathtaking", "groundbreaking", "renowned", "stunning", "must-visit". Use neutral descriptions.
  5. Vague attributions. "Experts believe", "Industry reports suggest", "Some critics argue". Name the source or delete.
  6. Formulaic challenges. "Despite challenges... continues to thrive." Replace with specific facts.
  1. 夸大重要性：诸如“关键时刻”“有力证明”“不断演变的格局”“为……奠定基础”“不可磨灭的印记”“根深蒂固”这类表述。去掉浮夸修饰，直接陈述事实。
  2. 无意义提及知名主体：不加上下文地罗列媒体机构。选一个，说明其具体观点。
  3. 表面化的-ing短语：诸如“强调……”“确保……”“反映……”“展示……”“促进……”。删除此类短语，或补充真实来源进行扩展。
  4. 宣传性语言：诸如“坐落于”“充满活力的”“令人惊叹的”“开创性的”“著名的”“惊艳的”“必去之地”。使用中性描述。
  5. 模糊归因：诸如“专家认为”“行业报告显示”“一些批评者指出”。明确来源或删除此类表述。
  6. 公式化的转折：诸如“尽管面临挑战……仍持续发展”。替换为具体事实。

Language

语言层面

  1. AI vocabulary. Additionally, crucial, delve, enduring, enhance, fostering, garner, interplay, intricate, landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore, vibrant. Replace with plain words.
  2. Copula avoidance. "serves as", "stands as", "boasts", "features". Just say "is" or "has".
  3. Negative parallelisms. "It's not just X, it's Y." State the point directly.
  4. Rule of three. Forcing ideas into groups of three. Use the natural number.
  5. Synonym cycling. Protagonist, main character, central figure, hero all in one paragraph. Pick one, repeat it.
  6. False ranges. "from X to Y" where X and Y aren't on a meaningful scale. List topics directly.
  1. AI常用词汇：Additionally、crucial、delve、enduring、enhance、fostering、garner、interplay、intricate、landscape（抽象义）、pivotal、showcase、tapestry（抽象义）、testament、underscore、vibrant。替换为平实词汇。
  2. 避免系动词：使用“serves as”“stands as”“boasts”“features”这类表达。直接用“is”或“has”即可。
  3. 否定式平行结构：诸如“这不仅仅是X，更是Y”。直接陈述核心观点。
  4. 强行凑三：将观点强行分成三组。使用自然的数量分组。
  5. 同义词循环：在同一段落中交替使用protagonist、main character、central figure、hero等词。选定一个，重复使用。
  6. 虚假范围：使用“从X到Y”但X和Y不在同一有效维度上。直接列出主题。

Style

风格层面

  1. Em dash overuse. Avoid em dashes entirely. Use periods or commas only (no parentheses, no en dashes, no hyphen-as-dash substitutes). Em dashes are an AI tell, and reaching for parentheses instead just trades one tell for another. If a thought needs separation, end the sentence or use a comma.
  2. Colon overuse. Colons are fine before a list or example. Not as mid-sentence connectors. "If you're coming from traditional automation: instead of registering event handlers, you describe conditions" adds nothing with the colon. Rewrite to let the point stand on its own without comparison framing. "Describing when the scheduler should fire works best as plain English." Same meaning, no crutch punctuation.
  3. Boldface overuse. Don't bold every proper noun or acronym.
  4. Inline-header lists. The tell is a bold label and colon that restates the line: "Performance: Performance improved...". Convert those to prose. A bold lead-in that ends in a period, names the item, and is followed by genuinely new detail ("Schema in TypeScript. Tables live in one file.") is fine, not a tell.
  5. Title case headings. Use sentence case.
  6. Decorative emojis. Remove from headings and bullets.
  7. Curly quotes. Replace with straight quotes.
  1. 过度使用破折号：完全避免使用破折号。仅使用句号或逗号（不使用括号、短破折号、连字符替代破折号）。破折号是AI生成的典型痕迹，而改用括号只是换了另一种痕迹。如果需要分隔想法，要么结束句子，要么使用逗号。
  2. 过度使用冒号：冒号适合用于列表或示例之前，不适合作为句中连接词。例如“如果你来自传统自动化领域：不用注册事件处理程序，而是描述条件”中的冒号毫无意义。重写文本，让观点无需对比框架即可独立成立。比如改成“用平实的英语描述调度程序应何时触发效果最佳。”意思相同，无需依赖辅助标点。
  3. 过度使用粗体：不要对每个专有名词或缩写都加粗。
  4. 内嵌标题式列表：典型痕迹是用粗体标签加冒号重复句子内容，例如“**性能：**性能有所提升……”。将此类内容转换为散文式表达。如果粗体开头以句号结尾，点明主题，并紧跟真正的新细节（例如“TypeScript中的Schema。所有表都存放在一个文件中。”），则是可行的，不属于AI痕迹。
  5. 标题大小写：使用句子大小写（仅句首字母大写）。
  6. 装饰性表情符号：从标题和项目符号中移除。
  7. 弯引号：替换为直引号。

Communication artifacts

沟通痕迹

  1. Chatbot phrases. "I hope this helps!", "Let me know if...", "Of course!", "Certainly!", "Found the smoking gun!" Remove.
  2. Cutoff disclaimers. "While specific details are limited..." Find sources or remove.
  3. Sycophantic tone. "Great question! You're absolutely right!" Respond directly.
  1. 聊天机器人用语：诸如“希望这对你有帮助！”“如有疑问请告知……”“当然！”“没问题！”“找到关键线索了！”。删除此类表述。
  2. 模糊免责声明：诸如“虽然具体细节有限……”。找到来源或删除此类表述。
  3. 谄媚语气：诸如“好问题！你完全正确！”。直接回应即可。

Filler

冗余内容

  1. Filler phrases. "In order to" becomes "To". "Due to the fact that" becomes "Because". "It is important to note that" gets deleted.
  2. Excessive hedging. "could potentially possibly be argued that it might" becomes "may".
  3. Generic conclusions. "The future looks bright." State specific plans or facts.
  1. 冗余短语：“In order to”改为“To”。“Due to the fact that”改为“Because”。“It is important to note that”直接删除。
  2. 过度模糊：诸如“could potentially possibly be argued that it might”简化为“may”。
  3. 通用结论：诸如“未来一片光明”。陈述具体计划或事实。

Jargon

行话术语

  1. Abstract metaphor nouns. Substrate, wedge, vector, locus, vantage, nexus, primitive (as noun), harness (as metaphor), surface (as in "API surface"), bedrock, scaffolding (as metaphor), modality, paradigm, gold-plating. These read as technical but usually have a plainer concrete word. "Substrate" becomes "base". "Wedge in" becomes "add". "Vector" becomes "way" or "method". "Gold-plating" becomes "more than the job needs". Pick the concrete word.
  1. 抽象隐喻名词：Substrate、wedge、vector、locus、vantage、nexus、primitive（名词义）、harness（隐喻义）、surface（如“API surface”）、bedrock、scaffolding（隐喻义）、modality、paradigm、gold-plating。这些词汇看似专业，但通常有更平实的具体词汇替代。例如“Substrate”改为“base”，“Wedge in”改为“add”，“Vector”改为“way”或“method”，“Gold-plating”改为“超出工作所需”。选择具体词汇。

Plain speech

平实表达

  1. Say the concrete thing. Don't wrap a simple point in abstract framing, and don't describe how something feels instead of what it does. "the database stays close at hand", "SQL you can read", "types that follow your schema" name a feeling. The fix names the mechanism or a number: "
    .toSQL()
    returns the exact string sent to the database", "a column rename fails the build". Ask what the sentence tells the reader to do or know, then write that. If you can't restate it as a concrete instruction, fact, or number, cut it.
  2. Shorten or split dense sentences. If the reader has to backtrack to parse a sentence, break it in two or drop clauses. One idea per sentence.
  3. Active voice. Prefer it. Catch "is/are/was/were + past participle" and name the actor: "queries are validated" becomes "the compiler validates queries", "the file is parsed by the loader" becomes "the loader parses the file". Passive is fine only when the actor is unknown or genuinely doesn't matter.
  4. Cut adverbs, or use a stronger verb. "runs quickly" becomes "is fast" or the number. "significantly improves" becomes the measured delta. An adverb propping up a weak verb means the verb is wrong.
  5. Prefer the plain word. "utilize" becomes "use", "leverage" becomes "use", "facilitate" becomes "help", "numerous" becomes "many", "in the event that" becomes "if". The fancier synonym is rarely clearer.
  1. 陈述具体事实：不要用抽象框架包装简单观点，也不要描述感受而非实际功能。诸如“数据库触手可及”“易读的SQL”“跟随Schema的类型”这类表述描述的是感受。修正后的表述应点明机制或数据：“
    .toSQL()
    返回发送给数据库的精确字符串”“列重命名会导致构建失败”。思考这句话要告诉读者什么操作或信息，然后直接写出来。如果无法将其重述为具体指令、事实或数据，就删除它。
  2. 拆分冗长复杂的句子：如果读者需要回溯才能理解句子，就将其拆分为两句或删除部分从句。一句表达一个观点。
  3. 主动语态：优先使用主动语态。识别“is/are/was/were + 过去分词”的被动结构，明确主语：“queries are validated”改为“编译器验证查询”，“the file is parsed by the loader”改为“加载器解析文件”。只有当主语未知或确实无关紧要时，才使用被动语态。
  4. 删除副词，或改用更强的动词：“runs quickly”改为“is fast”或具体数值。“significantly improves”改为具体的提升幅度。用副词支撑弱动词说明动词选得不对。
  5. 优先使用平实词汇：“utilize”改为“use”，“leverage”改为“use”，“facilitate”改为“help”，“numerous”改为“many”，“in the event that”改为“if”。花哨的同义词很少更清晰。