Back to Details

ds-unslop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Unslop

Unslop

Write clean as you draft. Then scan for these tells and rewrite. Keep the meaning and tone.
边写边保持表达简洁。写完后扫描以下痕迹并重写。保留原意和语气。

Tells to remove

需要去除的痕迹

Words
  • Inflated vocabulary: delve, crucial, pivotal, robust, seamless, leverage, utilize, showcase, underscore, tapestry, landscape, testament, vibrant, intricate. Use the plain word.
  • "Serves as", "stands as", "boasts". Say "is" or "has".
  • Abstract metaphor nouns: paradigm, north star, flywheel, substrate, bedrock. Name the concrete thing.
  • Adverbs that prop up weak verbs: "significantly improves". Give the number or a stronger verb.
Sentences
  • "Not just X, but Y." State Y.
  • Forced groups of three. Use the real count.
  • Trailing "-ing" clauses: "ensuring reliability", "highlighting the need". Delete them or make a real claim.
  • Vague sources: "experts say", "many believe". Name the source or cut it.
  • Filler: "in order to", "it is important to note that", "due to the fact that".
  • Stacked hedges: "could potentially". Pick one qualifier or none.
  • Passive voice that hides the actor. Name who does it.
  • Feelings instead of mechanisms. If a sentence fits any project's docs unchanged, cut it.
  • Generic endings: "the future looks bright". End on a fact or the next step.
  • Over-compressed fragments, arrows, and symbol shorthand. Write full sentences with articles and verbs.
Formatting
  • Em dashes. Use a period or a comma.
  • Colons used as mid-sentence connectors. Keep colons before lists.
  • Bold on every term, and "Label: label restated" bullets.
  • Title Case Headings. Use sentence case.
  • Decorative emojis and curly quotes.
Chat habits
  • Openers and closers: "Great question", "Certainly", "I hope this helps", "Let me know if".
  • Agreement as a reflex. Give your actual judgment.
Code comments
  • Comments that narrate the next line, banner comments, and commented-out code. Delete them.
  • Keep only comments that explain a reason the code cannot show.
词语
  • 浮夸词汇：delve、crucial、pivotal、robust、seamless、leverage、utilize、showcase、underscore、tapestry、landscape、testament、vibrant、intricate。改用平实的词。
  • “Serves as”“stands as”“boasts”。改用“是”或“有”。
  • 抽象隐喻类名词：paradigm、north star、flywheel、substrate、bedrock。说出具体事物。
  • 用副词支撑无力的动词：“significantly improves”。给出具体数字，或换用更有力的动词。
句子
  • “Not just X, but Y.”直接说明 Y。
  • 生硬罗列三个项目。写出实际数量。
  • 句尾悬空的“-ing”结构：“ensuring reliability”“highlighting the need”。删除这些结构，或写出明确的信息。
  • 来源含糊：“experts say”“many believe”。指出具体来源，否则删除。
  • 冗余填充语：“in order to”“it is important to note that”“due to the fact that”。
  • 叠加的模糊限定语：“could potentially”。只保留一个限定词，或全部删除。
  • 隐藏执行者的被动语态。说明由谁执行。
  • 只表达感受，却不说明机制。如果一句话可以原封不动地放进任何项目的文档中，就删除它。
  • 泛泛的结尾：“the future looks bright”。以事实或下一步行动收尾。
  • 过度压缩的片段、箭头和符号速记。写出包含冠词和动词的完整句子。
格式
  • 破折号。改用句号或逗号。
  • 在句子中间使用冒号连接内容。列表明细前可以保留冒号。
  • 给每个术语加粗，以及使用“Label: 重复标签内容”形式的列表项。
  • 标题使用 Title Case。改用 sentence case。
  • 装饰性 emoji 和弯引号。
聊天习惯
  • 开场和结尾套话：“Great question”“Certainly”“I hope this helps”“Let me know if”。
  • 习惯性赞同。给出你的实际判断。
代码注释
  • 复述下一行含义的注释、横幅式注释，以及被注释掉的代码。删除它们。
  • 仅保留能够说明代码无法呈现之原因的注释。

Rewrite procedure

重写步骤

  1. Name the reader and what they need to do or know after reading.
  2. Delete every sentence that does not serve that need.
  3. Replace synonyms for one thing with a single name. Use the real file, flag, or command name.
  4. Split sentences that carry two ideas. Vary sentence length.
  5. Put conditions before instructions: "To reset the cache, run 
    make clean
    ."
  6. Make every "it" and "this" point at one clear noun.
  7. Replace vague claims with a number, a command, or a concrete example.
  8. Reread once for the tells. A stiff sentence that follows every rule still needs a fix.
  1. 明确读者是谁，以及他们读完后需要做什么或了解什么。
  2. 删除每一句对该目标没有帮助的内容。
  3. 将同一事物的不同同义词统一为一个名称。使用真实的文件、标志或命令名称。
  4. 拆分包含两个观点的句子。调整句子长度。
  5. 将条件放在说明之前：“要重置缓存，请运行 
    make clean
    。”
  6. 让每个“it”和“this”都指向一个明确的名词。
  7. 用数字、命令或具体示例替换含糊的说法。
  8. 再读一遍，检查写作痕迹。如果一句话严格套用每条规则后仍显生硬，也需要修改。

Example

示例

Before: "This robust tool serves as a powerful way to seamlessly streamline your workflow, ensuring efficiency."
After: "
sync.sh
copies changed files to the server in about two seconds."
之前：“这个强大的工具可以无缝地简化工作流程，确保效率。”
之后：“
sync.sh
大约用两秒将变更的文件复制到服务器。”