Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

unslop

砍掉 AI 腔

Edit text to remove AI patterns.

改文本，去掉 AI 模式。

Process

流程

  1. Scan for the patterns below.

  2. Rewrite. Preserve meaning, match intended tone.

  3. 扫下面的模式。

  4. 改写。保意思，匹配目标语气。

Patterns to detect and fix

要检测并修的模式

Rule numbers are stable ids that other skills cite. A removed rule leaves a gap.

规则编号是其他 skill 引用的稳定 id。删掉规则会留下空号。

Content

内容

  1. Superficial -ing phrases. “highlighting…”, “ensuring…”, “reflecting…”, “showcasing…”, “fostering…”. Delete or expand with real sources.

  2. Vague attributions. “Experts believe”, “Industry reports suggest”, “Some critics argue”. Name the source or delete.

  3. 表面 -ing 短语。 “highlighting…”、“ensuring…”、“reflecting…”、“showcasing…”、“fostering…”。删掉，或用真实来源展开。

  4. 含糊归因。 “Experts believe”、“Industry reports suggest”、“Some critics argue”。点名来源或删。

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. Fancy ways to say “is”. “serves as”, “stands as”, “boasts”, “features”. Just say “is” or “has”.

  3. “Not just X, but Y.” State the point directly instead.

  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.

  7. AI 词表。 Additionally, crucial, delve, enduring, enhance, fostering, garner, interplay, intricate, landscape（抽象）, pivotal, showcase, tapestry（抽象）, testament, underscore, vibrant。换成白话。

  8. 花哨的「是」。 “serves as”、“stands as”、“boasts”、“features”。直接说 “is” 或 “has”。

  9. “Not just X, but Y.” 直接陈述要点。

  10. 三一律。 硬把想法塞成三组。用自然个数。

  11. 同义词轮换。 一段里主角、主要角色、中心人物、英雄全用。挑一个，重复它。

  12. 假区间。 “from X to 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). 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.

  8. 滥用 em dash。 完全避免。只用句号或逗号（不要括号、不要 en dash、不要用连字符当破折号）。想法要分开就结束句子或用逗号。

  9. 滥用冒号。 列表或例子前可以。别当句中连接。“If you’re coming from traditional automation: instead of…” 冒号没加信息。改写让要点自立，不要比较框。“Describing when the scheduler should fire works best as plain English.” 同样意思，无拐杖标点。

  10. 滥用加粗。 别每个专有名词或缩写都加粗。

  11. 行内标题列表。 征兆是加粗标签加冒号复述该行：“Performance: Performance improved…”。改成散文。以句号结尾、点名条目、后跟真正新细节的加粗引导（“Schema in TypeScript. Tables live in one file.”）可以，不是征兆。

  12. 标题用 Title Case。 用 sentence case。

  13. 装饰 emoji。 从标题和子弹去掉。

  14. 弯引号。 换成直引号。

Communication artifacts

沟通残留

  1. Chatbot phrases. “I hope this helps!”, “Let me know if…”, “Of course!”, “Certainly!”, “Found the smoking gun!” Remove.

  2. Sycophantic tone. “Great question! You’re absolutely right!” Respond directly.

  3. 聊天机器人套话。 “I hope this helps!”、“Let me know if…”、“Of course!”、“Certainly!”、“Found the smoking gun!” 删掉。

  4. 谄媚语气。 “Great question! You’re absolutely right!” 直接回应。

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.

  4. 填充短语。 “In order to” → “To”。“Due to the fact that” → “Because”。“It is important to note that” 删掉。

  5. 过度犹豫。 “could potentially possibly be argued that it might” → “may”。

  6. 空泛结论。 “The future looks bright.” 说具体计划或事实。

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, ratchet (as metaphor), evacuate (for moving code), endgame, north star, flywheel. 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”. “Ratchet” becomes the mechanism’s real name or “a limit that only tightens”. “Evacuate” becomes “move out”. “Endgame” becomes “the last phase”. Pick the concrete word.

  2. 抽象隐喻名词。 Substrate, wedge, vector, locus, vantage, nexus, primitive（作名词）, harness（作隐喻）, surface（如 “API surface”）, bedrock, scaffolding（作隐喻）, modality, paradigm, gold-plating, ratchet（作隐喻）, evacuate（指挪代码）, endgame, north star, flywheel。读起来像技术，通常有更白话的具体词。“Substrate” → “base”。“Wedge in” → “add”。“Vector” → “way” 或 “method”。“Gold-plating” → “超过这活需要的”。“Ratchet” → 机制真名或「只会收紧的限制」。“Evacuate” → “move out”。“Endgame” → “the last phase”。挑具体词。

Plain speech

白话

  1. Say what it does, not how it feels. “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. One more check: if the sentence could appear unchanged in another project’s docs, it says nothing about this one. 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.

  6. Mannered prose. Metaphor or flourish where a literal phrase exists: aphorisms (“wire it or delete it”), rhetorical fragments for effect, personified code (“the plan holds it”), figurative verbs (“rides along”, “stands on”), stock framing phrases. “A dial worth turning” becomes “a parameter worth varying”. Say what you mean. Rule 26 covers the metaphor nouns.

  7. Over-compression. Dropped articles, verbless fragments, symbol-speak, and abbreviations that make the reader decode instead of read. “Parser rejects bad date → exit 2, no write” becomes “The parser rejects a bad date, exits with code 2, and writes nothing.” Write whole sentences with their articles and verbs, and spell out arrows and abbreviations.

  8. 说它做什么，不说感觉如何。 “the database stays close at hand”、“SQL you can read”、“types that follow your schema” 在命名感觉。修法点名机制或数字：“.toSQL() returns the exact string sent to the database”、“a column rename fails the build”。问句子让读者做什么或知道什么，再写那个。复述不成具体指示、事实或数字就砍。再查：若句子原样能出现在另一项目文档里，就对本项目什么也没说。砍。

  9. 缩短或拆开密句。 读者要回看才能解析就拆成两句或丢从句。一句一个想法。

  10. 主动语态。 优先。抓住 “is/are/was/were + 过去分词” 并点名施事：“queries are validated” → “the compiler validates queries”，“the file is parsed by the loader” → “the loader parses the file”。仅当施事未知或真的无关时被动才行。

  11. 砍副词，或用更强动词。 “runs quickly” → “is fast” 或数字。“significantly improves” → 测到的增量。副词撑弱动词说明动词选错了。

  12. 优先白话词。 “utilize” → “use”，“leverage” → “use”，“facilitate” → “help”，“numerous” → “many”，“in the event that” → “if”。更花哨的同义词很少更清楚。

  13. 矫饰散文。 有字面短语却用隐喻或辞藻：格言（“wire it or delete it”）、为效果的修辞碎片、拟人化代码（“the plan holds it”）、比喻动词（“rides along”、“stands on”）、套框短语。“A dial worth turning” → “a parameter worth varying”。说你意思。规则 26 管隐喻名词。

  14. 过度压缩。 丢掉冠词、无动词碎片、符号腔、逼读者解码而非阅读的缩写。“Parser rejects bad date → exit 2, no write” → “The parser rejects a bad date, exits with code 2, and writes nothing.” 写完整句子，带冠词和动词，箭头和缩写写开。