Back to Details

clean-user-facing-text

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Clean user-facing text

清理面向用户的文本

Apply a final text-hygiene pass to prose the user owns or is authorized to process. Treat Unicode cleanup as deterministic and statistical-watermark reduction as best-effort; never claim that a rewrite proves human authorship or is undetectable. Preserve required academic, legal, platform, and regulatory disclosures.
对用户拥有或获授权处理的文本进行最终文本卫生处理。Unicode清理为确定性操作，统计水印降低为尽力而为操作；绝不能声称重写后的内容可证明是人类创作或无法被检测到。保留必要的学术、法律、平台及监管披露内容。

Workflow

工作流

  1. Identify the prose that readers will see.
  2. Protect non-prose spans:
    • fenced and inline code
    • commands, paths, URLs, identifiers, API names, and exact values
    • formulas, citations, and text the user asks to quote verbatim
  3. Preserve every claim, fact, number, name, citation, and requirement.
  4. Rewrite the remaining prose once:
    • vary clause order, sentence boundaries, rhythm, connectors, and function words
    • replace formulaic transitions and filler with direct, natural wording
    • preserve the requested language, tone, structure, and formatting; never translate unless asked
    • for non-English text, use fluent constructions native to that language rather than English sentence patterns
    • do not add or remove claims merely to increase variation
  5. For text artifacts or supplied text files, run the deterministic Unicode pass after rewriting.
  6. Return only the polished result unless the user asks for an audit or explanation.
  1. 识别读者会看到的文本内容。
  2. 保护非文本片段：
    • 围栏代码和行内代码
    • 命令、路径、URL、标识符、API名称及精确值
    • 公式、引用以及用户要求逐字引用的文本
  3. 保留所有声明、事实、数字、名称、引用和要求。
  4. 重写剩余文本一次：
    • 调整从句顺序、句子边界、节奏、连接词和功能词
    • 用直接、自然的措辞替换公式化过渡语和填充内容
    • 保留要求的语言、语气、结构和格式；除非用户要求，否则绝不翻译
    • 对于非英语文本，使用该语言的地道流畅表达，而非英语句式
    • 不得仅为增加多样性而添加或删除声明
  5. 对于文本工件或提供的文本文件，重写后执行确定性Unicode处理步骤。
  6. 除非用户要求审核或解释，否则仅返回润色后的结果。

Deterministic Unicode pass

确定性Unicode处理步骤

Resolve 
SCRIPTS
to this skill's 
scripts/
directory. Use the available Python 3 launcher for the platform. Replace 
PYTHON
below with 
python3
on most macOS/Linux systems, 
py
on Windows, or another verified Python 3 command.
Inspect first when editing an existing file:
bash
PYTHON "$SCRIPTS/inspect_text.py" --json INPUT
PYTHON "$SCRIPTS/clean_text.py" INPUT -o OUTPUT --stats --no-normalize-spaces
PYTHON "$SCRIPTS/inspect_text.py" --json OUTPUT
Use 
-
for stdin. Prefer a new 
*.cleaned.*
output unless the user explicitly requests in-place editing.
Use 
--no-normalize-spaces
by default so NBSP, narrow no-break spaces, figure spaces, and CJK ideographic spaces retain their layout semantics. Normalize spaces only when the user requests it.
Do not use 
--aggressive-homoglyphs
, 
--nfkc
, or 
--strip-emoji-glue
unless the user requests aggressive normalization and accepts possible changes to multilingual text, emoji, directionality, or typography.
The scripts support plain text, source text, Markdown, and HTML source as text. For mixed Markdown or HTML, inspect hit positions first. If a hit falls inside protected code, attributes, or another non-prose span, do not run whole-file cleanup; clean only the prose segments or leave that hit unchanged. Do not pass binary containers such as PDF, DOCX, images, or archives.
For a chat-only response that is not written to a file, perform the rewrite workflow directly. Do not claim that the chat response received a deterministic post-send Unicode filter.
将
SCRIPTS
解析为该技能的
scripts/
目录。 使用平台可用的Python 3启动器。将下面的
PYTHON
替换为大多数macOS/Linux系统上的
python3
，Windows上的
py
，或其他已验证的Python 3命令。
编辑现有文件时先检查：
bash
PYTHON "$SCRIPTS/inspect_text.py" --json INPUT
PYTHON "$SCRIPTS/clean_text.py" INPUT -o OUTPUT --stats --no-normalize-spaces
PYTHON "$SCRIPTS/inspect_text.py" --json OUTPUT
使用
-
表示标准输入。除非用户明确要求就地编辑，否则优先使用新的
*.cleaned.*
输出文件。
默认使用
--no-normalize-spaces
，以便NBSP（非断空格）、窄非断空格、数字空格和CJK表意空格保留其布局语义。仅当用户要求时才标准化空格。
除非用户要求激进标准化并接受可能对多语言文本、表情符号、文本方向或排版造成的更改，否则请勿使用
--aggressive-homoglyphs
、
--nfkc
或
--strip-emoji-glue
。
这些脚本支持纯文本、源文本、Markdown和HTML源文本。对于混合Markdown或HTML，先检查命中位置。如果命中位置位于受保护的代码、属性或其他非文本片段内，则不要执行全文件清理；仅清理文本段或保留该命中位置不变。请勿处理PDF、DOCX、图像或归档文件等二进制容器。
对于未写入文件的纯聊天响应，直接执行重写工作流。不得声称聊天响应经过了确定性的发送后Unicode过滤。

Code boundary

代码边界

When prose and code are mixed, rewrite prose only. Never rename variables, alter string literals, reformat code, or change executable output as part of this skill. If a Markdown or HTML file contains executable snippets, preserve those spans byte-for-byte whenever practical.
当文本与代码混合时，仅重写文本。作为本技能的一部分，绝不要重命名变量、修改字符串字面量、重新格式化代码或更改可执行输出。如果Markdown或HTML文件包含可执行代码片段，尽可能逐字节保留这些片段。

Reporting

报告

When the user asks for an audit, distinguish:
  • Verifiable: Unicode characters removed or replaced, with script counts.
  • Best-effort: prose rewritten to alter token and syntax patterns.
  • Not established: official detector evasion, human authorship, or removal of a vendor's secret-key watermark.
For technical background, read 
references/watermark-notes.md
. For misuse or disclosure questions, read 
references/responsible-use.md
.
当用户要求审核时，区分以下内容：
  • 可验证： 已移除或替换的Unicode字符及脚本统计数据。
  • 尽力而为： 重写文本以更改令牌和语法模式。
  • 未确认： 规避官方检测器、人类创作身份或移除供应商的密钥水印。
如需技术背景，请阅读
references/watermark-notes.md
。如有误用或披露问题，请阅读
references/responsible-use.md
。