de-slopify
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDe-Slopify — Remove AI Writing Artifacts
De-Slopify — 去除AI写作痕迹
Purpose: Make your documentation sound like it was written by a human, not an LLM.Key Insight: You can't do this with regex or a script—it requires manual, systematic review of each line.
用途： 让你的文档听起来像是真人撰写的，而非LLM生成的。核心见解： 你无法通过正则表达式或脚本完成这项工作——需要逐行进行人工、系统性的审核。
What is "AI Slop"?
什么是“AI劣质文本（AI Slop）”？
AI slop refers to writing patterns that LLMs produce disproportionately more commonly than human writers. These patterns make text sound inauthentic and "cringe."
AI劣质文本指的是LLM生成的、远多于人类作家使用的写作模式。这些模式会让文本听起来不真实、令人尴尬。
Common Tells
常见特征
| Pattern | Problem |
|---|---|
| Emdash overuse | LLMs love emdashes—they use them constantly—even when other punctuation works better |
| "It's not X, it's Y" | Formulaic contrast structure |
| "Here's why" | Clickbait-style lead-in |
| "Here's why it matters:" | Same energy |
| "Let's dive in" | Forced enthusiasm |
| "In this guide, we'll..." | Overly formal setup |
| "It's worth noting that..." | Unnecessary hedge |
| "At its core..." | Pseudo-profound opener |
| 模式 | 问题 |
|---|---|
| 过度使用破折号 | LLM非常喜欢使用破折号——频繁使用——即便其他标点符号更合适 |
| “不是X，而是Y” | 公式化的对比结构 |
| “原因如下” | 标题党式的引入 |
| “这一点很重要的原因：” | 类似的生硬风格 |
| “让我们深入探讨” | 刻意营造的虚假热情 |
| “在本指南中，我们将……” | 过于正式的冗余开篇 |
| “值得注意的是……” | 不必要的铺垫性表述 |
| “从本质上来说……” | 故作深刻的开场白 |
THE EXACT PROMPT — De-Slopify Documentation
精准提示词 — 去除文档中的AI劣质文本
I want you to read through the complete text carefully and look for any telltale signs of "AI slop" style writing; one big tell is the use of emdash. You should try to replace this with a semicolon, a comma, or just recast the sentence accordingly so it sounds good while avoiding emdash.
Also, you want to avoid certain telltale writing tropes, like sentences of the form "It's not [just] XYZ, it's ABC" or "Here's why" or "Here's why it matters:". Basically, anything that sounds like the kind of thing an LLM would write disproportionately more commonly that a human writer and which sounds inauthentic/cringe.
And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way. Use ultrathink.I want you to read through the complete text carefully and look for any telltale signs of "AI slop" style writing; one big tell is the use of emdash. You should try to replace this with a semicolon, a comma, or just recast the sentence accordingly so it sounds good while avoiding emdash.
Also, you want to avoid certain telltale writing tropes, like sentences of the form "It's not [just] XYZ, it's ABC" or "Here's why" or "Here's why it matters:". Basically, anything that sounds like the kind of thing an LLM would write disproportionately more commonly that a human writer and which sounds inauthentic/cringe.
And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way. Use ultrathink.Why Manual Review is Required
为什么需要人工审核？
The prompt explicitly states:
"And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way."
Reasons:
- Context matters — Sometimes an emdash is actually the right choice
- Recasting sentences — Often the fix isn't substitution but rewriting
- Tone consistency — Need to maintain voice throughout
- Judgment calls — Some patterns are fine in moderation
提示词中明确说明：
"你无法通过正则表达式或脚本完成这项工作，必须逐行人工阅读文本，并以系统、有条理、认真的方式手动修改。"
原因：
- 上下文至关重要 — 有时破折号确实是合适的选择
- 改写句子 — 通常的解决方案不是替换，而是改写
- 语气一致性 — 需要全程保持统一的语气
- 判断决策 — 有些模式在适度使用时是没问题的
Emdash Alternatives
破折号的替代方案
When you encounter an emdash (—), consider:
| Original | Alternative |
|---|---|
| |
| |
| |
| |
Sometimes the best fix is to split into two sentences or restructure entirely.
当你遇到破折号（—）时，可以考虑：
| 原文 | 替代方案 |
|---|---|
| |
| |
| |
| |
有时最好的解决方案是拆分成两个句子或彻底重构。
Phrases to Eliminate or Rewrite
需要删除或改写的短语
"Here's why" family
“原因如下”系列
- "Here's why" → Just explain why directly
- "Here's why it matters" → Explain the importance inline
- "Here's the thing" → Usually can be deleted entirely
- “原因如下” → 直接解释原因
- “这一点很重要的原因” → 直接在文中说明重要性
- “关键是” → 通常可以直接删除
Contrast formulas
对比公式
- "It's not X, it's Y" → "This is Y" or explain the distinction differently
- "It's not just X, it's also Y" → "This does X and Y" or similar
- “不是X，而是Y” → “这是Y” 或用其他方式解释区别
- “不只是X，还是Y” → “这可以实现X和Y” 或类似表达
Forced enthusiasm
刻意营造的热情
- "Let's dive in!" → Just start
- "Let's get started!" → Just start
- "Excited to share..." → Just share it
- “让我们深入探讨！” → 直接开始
- “让我们开始吧！” → 直接开始
- “很高兴分享……” → 直接分享内容
Pseudo-profound openers
故作深刻的开场白
- "At its core..." → Usually can be deleted
- "Fundamentally..." → Often unnecessary
- "In essence..." → Just say the essence
- “从本质上来说……” → 通常可以删除
- “根本上……” → 往往不必要
- “本质上……” → 直接说明核心内容
Unnecessary hedges
不必要的铺垫
- "It's worth noting that..." → Just note it
- "It's important to remember..." → Just state the fact
- "Keep in mind that..." → Often deletable
- “值得注意的是……” → 直接说明内容
- “重要的是要记住……” → 直接陈述事实
- “请记住……” → 通常可以删除
Before and After Examples
前后对比示例
Example 1: Emdash Overuse
示例1：过度使用破折号
Before (sloppy):
This tool—which we built from scratch—handles everything automatically—from parsing to output.After (clean):
This tool handles everything automatically, from parsing to output. We built it from scratch.优化前（劣质）：
This tool—which we built from scratch—handles everything automatically—from parsing to output.优化后（简洁）：
This tool handles everything automatically, from parsing to output. We built it from scratch.Example 2: "Here's why" Pattern
示例2：“原因如下”模式
Before (sloppy):
We chose Rust for this component. Here's why: performance matters, and Rust delivers.After (clean):
We chose Rust for this component because performance matters.优化前（劣质）：
We chose Rust for this component. Here's why: performance matters, and Rust delivers.优化后（简洁）：
We chose Rust for this component because performance matters.Example 3: Contrast Formula
示例3：对比公式
Before (sloppy):
It's not just a linter—it's a complete code quality system.After (clean):
This is a complete code quality system, not just a linter.Or even better:
This complete code quality system goes beyond basic linting.优化前（劣质）：
It's not just a linter—it's a complete code quality system.优化后（简洁）：
This is a complete code quality system, not just a linter.或者更好的表达：
This complete code quality system goes beyond basic linting.Example 4: Forced Enthusiasm
示例4：刻意营造的热情
Before (sloppy):
undefined优化前（劣质）：
undefinedGetting Started
Getting Started
Let's dive in! We're excited to help you get up and running with our amazing tool.
**After (clean):**Let's dive in! We're excited to help you get up and running with our amazing tool.
**优化后（简洁）：**Getting Started
Getting Started
Install the tool and run your first command in under a minute.
---Install the tool and run your first command in under a minute.
---When to De-Slopify
何时进行AI劣质文本去除？
Best Times
最佳时机
- Before publishing a README
- Before releasing documentation
- After AI-assisted writing sessions
- During documentation reviews
- 发布README之前
- 发布文档之前
- AI辅助写作之后
- 文档审核期间
Files to Check
需要检查的文件
- README.md
- CONTRIBUTING.md
- API documentation
- Blog posts
- Any public-facing text
- README.md
- CONTRIBUTING.md
- API文档
- 博客文章
- 任何面向公众的文本
Integration with Workflow
融入工作流
As Part of Bead Workflow
作为Bead工作流的一部分
bash
bd create "De-slopify README.md" -t docs -p 3
bd create "De-slopify API documentation" -t docs -p 3bash
bd create "De-slopify README.md" -t docs -p 3
bd create "De-slopify API documentation" -t docs -p 3As Final Pass Before Commit
提交前的最终检查
Now, before we commit, please read through README.md and look for any telltale signs of "AI slop" style writing...Now, before we commit, please read through README.md and look for any telltale signs of "AI slop" style writing...What NOT to Fix
无需修改的内容
Some things are fine even if they seem "AI-like":
- Technical accuracy — Don't sacrifice correctness for style
- Necessary structure — Headers, lists, etc. are fine
- Clear explanations — Being thorough isn't slop
- Code examples — Focus on prose, not code
有些内容即便看起来“像AI生成的”也无需修改：
- 技术准确性 — 不要为了风格牺牲正确性
- 必要结构 — 标题、列表等没问题
- 清晰的解释 — 内容详尽不等于劣质文本
- 代码示例 — 重点关注说明文字，而非代码
Complete Prompt Reference
完整提示词参考
Main De-Slopify Prompt
主要De-Slopify提示词
I want you to read through the complete text carefully and look for any telltale signs of "AI slop" style writing; one big tell is the use of emdash. You should try to replace this with a semicolon, a comma, or just recast the sentence accordingly so it sounds good while avoiding emdash.
Also, you want to avoid certain telltale writing tropes, like sentences of the form "It's not [just] XYZ, it's ABC" or "Here's why" or "Here's why it matters:". Basically, anything that sounds like the kind of thing an LLM would write disproportionately more commonly that a human writer and which sounds inauthentic/cringe.
And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way. Use ultrathink.I want you to read through the complete text carefully and look for any telltale signs of "AI slop" style writing; one big tell is the use of emdash. You should try to replace this with a semicolon, a comma, or just recast the sentence accordingly so it sounds good while avoiding emdash.
Also, you want to avoid certain telltale writing tropes, like sentences of the form "It's not [just] XYZ, it's ABC" or "Here's why" or "Here's why it matters:". Basically, anything that sounds like the kind of thing an LLM would write disproportionately more commonly that a human writer and which sounds inauthentic/cringe.
And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way. Use ultrathink.Quick Version (for minor touch-ups)
精简版（用于小幅润色）
Review this text and remove any AI slop patterns: excessive emdashes, "Here's why" constructions, "It's not X, it's Y" formulas, and other LLM writing tells. Recast sentences to sound more naturally human. Use ultrathink.Review this text and remove any AI slop patterns: excessive emdashes, "Here's why" constructions, "It's not X, it's Y" formulas, and other LLM writing tells. Recast sentences to sound more naturally human. Use ultrathink.