stop-slop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Stop slop

摒弃机器感冗余文案

Use this skill only for durable prose: text that will be saved, shipped, published, committed, or pasted outside chat. Do not use it for ordinary assistant replies, progress updates, or final answers unless that response contains a durable artifact; then apply it only to the artifact.
"Slop" is prose that reads as machine-written. A banned-word list catches "delve", "tapestry", and "in today's landscape", but it misses problems with rhythm and rhetorical scaffolding. Most useful signals are structural.
Avoid two failure modes:
  1. Slop uses constant rhetorical framing. It reassures the reader and resolves each thought into a balanced contrast or tidy maxim.
  2. Over-correction makes every sentence flat and informational. Uniform rhythm is also a machine-written signal.
Write plain, specific, varied prose that explains concrete mechanisms. One brief expression of personality per section is fine.
本技能仅适用于需长期留存的文案:即会被保存、发布、提交或粘贴到聊天外的文本。请勿将其用于普通助手回复、进度更新或最终答案,除非回复中包含需长期留存的文案制品;此时仅对该制品应用本技能。
“冗余文案(slop)”指读起来像机器生成的文字。禁用词列表可以识别“delve”“tapestry”“in today's landscape”这类词汇,但无法察觉节奏和修辞结构方面的问题。最有用的判断信号是结构层面的。
需避免两种失败模式:
  1. 冗余文案使用固定的修辞框架。它会安抚读者,并将每个想法转化为平衡的对比或工整的格言。
  2. 过度修正会让每个句子都平淡乏味、只讲信息。统一的节奏也是机器生成文字的特征。
撰写直白、具体、多样的文案,解释具体机制。每个段落可以有一处简短的个性化表达。

The core test

核心测试

After an edit, ask whether every fact is still present. A shorter version that keeps every fact removed slop. A rewrite that drops information changes the content rather than its style.
编辑完成后,检查是否所有事实都保留了下来。保留所有事实的精简版本即为去除了冗余文案的版本;而删除信息的改写则是改变了内容,而非调整风格。

The structural tells

结构识别点

Scan for these.
references/structures.md
covers each in depth with kill/keep tests; this is the working list.
  1. Virtue or character framing. Delete claims that a subject is honest, trustworthy, principled, or humble. State what it does and let the mechanism show its character.
  2. Manufactured antithesis. Remove "X, not Y" when Y is a strawman or mood. Keep it when both sides name real and distinct facts.
  3. Aphorism openers and closers. Cut tidy maxims that repeat the surrounding facts.
  4. Decorative groups of three. Keep a three-item list only when the content has exactly three real items.
  5. Dramatic setup and payoff. State the information directly instead of staging it for suspense.
  6. Uniform clipped headers. Vary the structure and use plain noun phrases where they fit.
  7. Uniform rhythm. Allow some sentences to be flat and informational. Natural prose varies in length and emphasis.
排查以下结构。
references/structures.md
深入介绍了每个点的取舍测试;以下是实用列表:
  1. 美德或品格框架:删除关于某主体诚实、可信、有原则或谦逊的表述。直接说明它的功能,让机制体现其特质。
  2. 刻意制造的对立:当Y是稻草人式表述或情绪性表达时,删除“X,而非Y”的结构。当双方都指代真实且不同的事实时,保留该结构。
  3. 格言式开头或结尾:删除重复周边事实的工整格言。
  4. 装饰性的三点式列表:仅当内容恰好包含三个真实条目时,才保留三点式列表。
  5. 戏剧性铺垫与收尾:直接陈述信息,而非为制造悬念而铺垫。
  6. 统一的简短标题:调整结构,在合适的地方使用直白的名词短语。
  7. 统一的节奏:允许部分句子平淡、只讲信息。自然的文案在长度和侧重点上会有所变化。

Discriminate, do not carpet-bomb

精准甄别,而非全盘否定

The "X, not Y" structure is frequent and easy to remove too broadly. Examine what each side contributes:
  • KILL: "a gate you govern, not a bot you tolerate" (the second half is a strawman invented for cadence).
  • KEEP: "gates block, advisors comment" and "gates fail closed, advisors fail open" (both halves name real, distinct, opposed behaviors).
Apply the same test to fragments and short sentences. Remove manufactured ones, but keep useful variation.
“X,而非Y”结构很常见,容易被过度删除。需审视双方的实际贡献:
  • 删除:“由你掌控的闸门,而非需忍受的机器人”(后半部分是为了韵律而编造的稻草人式表述)。
  • 保留:“闸门用于拦截,顾问用于评论”以及“闸门故障时关闭,顾问故障时开放”(两部分都指代真实、明确、对立的行为)。
对片段和短句应用同样的测试。删除刻意制造的内容,但保留有用的变化。

Voice anchor (highest leverage)

语气锚点(最高优先级)

A target voice is more useful than the instruction "remove AI tells". Read two or three representative paragraphs before editing. Match their sentence length, comment density, and idiom. Without a sample, write like the engineer who built the system and respects the reader's time.
设定目标语气比“去除AI痕迹”的指令更有用。编辑前先阅读2-3段代表性段落,匹配其句子长度、注释密度和惯用表达。如果没有样本,则以构建系统的工程师的口吻写作,尊重读者的时间。

Workflow

工作流程

  1. Read a voice anchor from the same author or product when one exists.
  2. Read for meaning. Mark sentences that add rhetoric without adding facts.
  3. Rewrite each marked sentence. Keep every fact while removing unnecessary framing.
  4. Keep real contrasts and occasional personality. Do not flatten useful variation.
  5. Preserve code, commands, data, tables, and quoted third-party material.
  6. Read the result from start to finish. Restore variation if every sentence has the same rhythm.
  1. 若存在同一作者或产品的语气样本,先阅读该锚点文本。
  2. 通读原文理解含义,标记那些只添加修辞而未增加事实的句子。
  3. 重写每个标记的句子。保留所有事实,同时去除不必要的框架。
  4. 保留真实的对比和偶尔的个性化表达。不要消除有用的变化。
  5. 保留代码、命令、数据、表格和引用的第三方内容。
  6. 从头到尾通读结果。如果所有句子节奏一致,恢复适当的变化。

Mechanics

格式规范

Follow ASD-STE100 Simplified Technical English in spirit. Do not enforce its controlled dictionary unless the user asks for strict compliance.
  • Plain ASCII only. No em dashes, no en dashes, and no literal
    --
    used as a dash in prose. Recast with a comma, a colon, parentheses, or two sentences. Leave
    --flag
    forms inside commands and code alone.
  • Use one term for each concept.
  • Prefer active voice and direct commands.
  • Keep each paragraph on one topic.
  • Put one action in each procedural step. Keep procedural sentences to 20 words or fewer when practical.
遵循ASD-STE100简化技术英语的核心精神。除非用户要求严格合规,否则无需强制执行其受控词典。
  • 仅使用纯ASCII字符。不要使用长破折号、短破折号,也不要在文案中用字面的
    --
    代替破折号。改用逗号、冒号、括号或拆分为两个句子。命令和代码中的
    --flag
    形式无需修改。
  • 每个概念使用统一术语。
  • 优先使用主动语态和直接指令。
  • 每个段落围绕一个主题展开。
  • 每个步骤只包含一个动作。实际操作中,尽量将步骤句子控制在20词以内。

References

参考资料

  • references/structures.md
    : the structural tells in depth, each with a kill-or-keep test and a rewrite.
  • references/phrases.md
    : the lexical tells (a lower-priority backstop; the structure matters more than the vocabulary).
  • references/examples.md
    : before and after rewrites from a real landing page.
  • references/structures.md
    :深入介绍结构识别点,每个点都包含取舍测试和改写示例。
  • references/phrases.md
    :词汇识别点(优先级较低的后备方案;结构比词汇更重要)。
  • references/examples.md
    :真实落地页的改写前后示例。