Back to Details

stss

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Stop That Shit Slop

停止那种狗屁废话

别再废话。
Make the point without writing for an imaginary critic. Preserve limitations that change what the reader understands or decides.
别再废话。
直接表达重点，不要像是在写给一个 imaginary critic。保留会改变读者理解或决策的必要限制。

Stay in scope

严格限定范围

Reduce defensive wording in reader-facing prose, including captions and introductions. Do not classify text as AI-written, promise to remove an "AI voice," humanize unrelated prose, or perform a general style cleanup.
Judge sentences by their reader use, including sentences introduced during drafting. A request to describe a project's evolution calls for that history; it does not by itself call for an account of how the article's sources were checked.
减少面向读者的文字（包括字幕说明和引言）中的防御性措辞。不要判断文本是否由 AI 写成，不要承诺消除所谓的“AI 腔”，不要将无关文字改得更像人写，也不要进行通用风格清理。
根据句子的读者用途来判断，包括起草过程中新增的句子。用户要求描述项目的演进过程，意味着需要讲述这段历史；这本身并不意味着需要说明如何核查文章的信息来源。

Select the mode

选择模式

  • rewrite
    : Return a tighter version. This is the default when the user provides text without a mode.
  • audit
    : Identify defensive writing and propose the smallest useful fix. Do not rewrite the full text.
Follow an explicit mode. Infer the mode from the request only when none is given.
For a drafting request, create the requested artifact from the supplied material and apply the rewrite checks before returning it.
  • rewrite
    ：返回更紧凑的版本。用户只提供文本而未指定模式时，默认使用此模式。
  • audit
    ：识别防御性写作，并提出最小且有用的修改方案。不要重写全文。
遵循用户明确指定的模式。仅在用户未指定模式时，才根据请求推断模式。
对于起草请求，根据所提供的材料创建所需内容，并在返回前应用改写检查。

Record the claims

记录主张

Before editing, build a private Claim Ledger from the supplied material:
  • facts and numbers;
  • named actors and sources;
  • evidence strength;
  • stated uncertainty and scope;
  • what the reader needs to understand or do.
Do not print the ledger unless the user asks for it. Do not add facts, sources, numbers, certainty, or causality.
Keeping facts accurate does not require printing every editorial note. Keep verification logs and source-checking process in working notes unless the reader needs them. Preserve useful attribution, actual methods, and conditions that affect a claim.
编辑前，根据所提供的材料建立一份私密的 Claim Ledger：
  • 事实和数字；
  • 指名的参与者和信息来源；
  • 证据强度；
  • 已声明的不确定性和适用范围；
  • 读者需要了解或完成的事项。
除非用户要求，否则不要输出该 Claim Ledger。不要添加事实、信息来源、数字、确定性或因果关系。
保持事实准确，并不意味着需要输出每一条编辑备注。除非读者确实需要，否则应将核查日志和信息来源检查过程留在工作笔记中。保留有用的归因、实际采用的方法，以及会影响主张的条件。

Test each defensive sentence

测试每个防御性句子

Apply the Sentence Consumer Test:
  1. Who will use this sentence?
  2. What understanding or decision does it change for this reader?
  3. What becomes false or misleading if it is removed?
Choose one action:
  • DROP
    : It only narrates diligence, anticipates criticism, apologizes, or says what the document does not attempt.
  • CALIBRATE
    : It contains real uncertainty but uses stacked hedges. Keep one precise limitation.
  • RELOCATE
    : The reader needs it beside a particular claim, or only the editor needs it in working notes. Choose the destination by its consumer; moving an unnecessary disclaimer to a footnote does not make it useful.
  • KEEP
    : It changes the meaning, evidence strength, attribution, or a legal, safety, financial, methodological, contractual, or scope decision.
Do not decide from a keyword alone. The same phrase can be waste in one context and necessary in another.
应用 Sentence Consumer Test：
  1. 谁会使用这个句子？
  2. 它会改变该读者对内容的理解或决策吗？
  3. 删除它后，什么内容会变得不准确或具有误导性？
选择一种处理方式：
  • DROP
    ：句子只是在叙述勤勉程度、预设批评、表达歉意，或说明文档不打算做什么。
  • CALIBRATE
    ：句子包含真实的不确定性，但使用了层层对冲。保留一个精确的限制说明。
  • RELOCATE
    ：读者需要它紧邻某项主张，或者只有编辑需要在工作笔记中保留它。根据使用者选择放置位置；将不必要的免责声明移到脚注并不会让它变得有用。
  • KEEP
    ：它会影响含义、证据强度、归因，或涉及法律、安全、财务、方法、合同或范围方面的决策。
不要仅凭关键词作判断。同一句话在一个语境中可能是废话，在另一个语境中却可能是必要的。

Rewrite

改写

  1. Lead with the requested subject, claim, decision, or proposal.
  2. State scope positively: say what the work covers.
  3. Replace stacked hedges with one evidence-matched qualifier.
  4. Remove internal process narration unless the process is requested or material.
  5. Put a necessary limitation beside the claim it limits.
  6. Check the complete artifact, including captions and assistant-added prefaces, against the Claim Ledger and Sentence Consumer Test. Do not reintroduce dropped defenses in the delivery note.
Return only the requested artifact unless the user asks for commentary. If the text is already direct and faithful, return it unchanged.
  1. 以用户要求的主题、主张、决策或提案开篇。
  2. 正面陈述适用范围：说明工作涵盖的内容。
  3. 用一个与证据程度匹配的限定词替代层层对冲。
  4. 删除内部流程叙述，除非用户要求了解该流程，或该流程具有实质影响。
  5. 将必要的限制放在其所限制的主张旁边。
  6. 根据 Claim Ledger 和 Sentence Consumer Test 检查完整内容，包括字幕说明和助手添加的前言。不要在交付说明中重新引入已删除的防御性内容。
除非用户要求评论，否则只返回所需内容。如果文本已经直接且忠实，则原样返回。

Audit

审校

Report only actionable findings. For each finding, give:
  • the span or sentence;
  • DROP
    , 
    CALIBRATE
    , 
    RELOCATE
    , or 
    KEEP
    ;
  • the reader's interpretation or decision affected;
  • the smallest replacement when one is needed.
Use 
NO_DECISION_CONSUMER
when a sentence serves neither reader understanding nor a decision. If there are no actionable findings, say so and stop.
只报告可采取行动的发现。对于每项发现，提供：
  • 相关片段或句子；
  • DROP
    、
    CALIBRATE
    、
    RELOCATE
    或 
    KEEP
    ；
  • 受影响的读者理解或决策；
  • 必要时提供最小替换方案。
如果某个句子既不影响读者理解，也不影响任何决策，则使用 
NO_DECISION_CONSUMER
。如果没有可采取行动的发现，说明这一点并停止。

Check the claim diff

检查主张差异

Before returning the result, verify:
  • no supplied fact, number, source, or actor disappeared without reason;
  • no new fact, number, source, or actor appeared;
  • uncertainty did not become certainty;
  • correlation did not become causation;
  • a requested or meaning-changing limitation remains visible.
Run one claim-preserving pass. Do not add a score, a probability that text is AI-written, a change diary, or repeated self-review.
Read references/examples.md when the boundary is ambiguous or the user asks for examples.
返回结果前，验证：
  • 所提供的事实、数字、信息来源或参与者没有在无合理依据的情况下消失；
  • 没有出现新的事实、数字、信息来源或参与者；
  • 不确定性没有被夸大为确定性；
  • 相关性没有被错误表述为因果关系；
  • 用户要求的限制或会影响含义的限制仍然清晰可见。
执行一次保持主张不变的检查。不要添加评分、文本由 AI 写成的主观概率、修改记录或重复的自我审查。
当边界不明确或用户要求提供示例时，阅读 references/examples.md。