clarify

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Context: this sub-skill is one lens of the broader

ui-craft

skill. If the

ui-craft

skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Clarify the copy in

$ARGUMENTS

. Load the

ui-craft

skill.

Default mode: critique, not edit. Return the copy diff in a Review Format table. Only apply changes if the user says "apply".

Checklist — walk the UI and flag every instance:

Button labels — verb + object. "Send invite" > "Submit". "Delete project" > "Delete". Never "OK", "Submit", "Click here".
Errors — inline, specific, actionable. "Email already in use — sign in or use another address." Never "Something went wrong."
Empty states — one line explaining why empty + one CTA. "No projects yet. Create your first." not "It's empty here!"
Form hints — below the field, persistent, not just validation-triggered. "Must include a number and a symbol" as helper text, not as an error after submit.
Confirmation language — past tense, subject-first. "Project deleted." > "Successfully deleted project."
Destructive actions — the noun lives in the button. "Delete {projectName}" > "Delete". The dialog confirms; the button commits.
Case — sentence case by default. Title Case only for branded product names. Never ALL CAPS (exception: 11-13px category labels, already in SKILL.md).
Voice — clear > clever. Active voice. Short sentences. Real words ("cancel" not "discontinue", "start" not "initiate").

Knob-agnostic — clarity is not tunable. Run the full checklist regardless of CRAFT_LEVEL.

References to read:

references/copy.md

(microcopy voice + patterns),

references/accessibility.md

(error message expectations for screen readers).

Output format — the Review Format table:

Before	After	Why

Prioritize by impact (errors and destructive actions first, then CTAs, then helper copy). End with a one-paragraph summary of the overall voice shift. If the user says "apply", edit the code and re-print the table with file paths.

Next step:

/critique

— copy changes shift hierarchy; re-read the surface after (rung 1).

背景： 本子技能是更广泛的

ui-craft

技能的一个视角。如果同时安装了

ui-craft

技能，请先阅读其SKILL.md文档了解Discovery + Anti-Slop + Craft Test相关内容，再应用以下特定视角。

澄清

$ARGUMENTS

中的文案。加载

ui-craft

技能。

默认模式：批评建议，而非直接编辑。 以「审查格式」表格返回文案差异。仅当用户说出「apply」时才应用修改。

检查清单——遍历UI并标记所有不符合项：

按钮标签 —— 采用「动词+宾语」结构。「Send invite」优于「Submit」；「Delete project」优于「Delete」。严禁使用「OK」「Submit」「Click here」这类表述。
错误提示 —— 行内展示、具体明确、可执行。例如「Email already in use — sign in or use another address.」，严禁出现「Something went wrong.」这类模糊表述。
空状态 —— 一行说明为空原因 + 一个CTA。例如「No projects yet. Create your first.」，而非「It's empty here!」
表单提示 —— 位于输入框下方，持续展示，而非仅在触发校验时显示。例如将「Must include a number and a symbol」作为辅助文本，而非提交后才弹出的错误提示。
确认文案 —— 使用过去时态，主语前置。「Project deleted.」优于「Successfully deleted project.」
破坏性操作 —— 名词需放在按钮文案中。「Delete {projectName}」优于「Delete」。由对话框承担确认作用，按钮负责执行操作。
大小写规范 —— 默认使用sentence case。仅品牌产品名使用Title Case。严禁使用ALL CAPS（例外：11-13px的分类标签，已在SKILL.md中说明）。
语气风格 —— 清晰优先于巧思。使用主动语态、短句，选用平实常用的词汇（例如用「cancel」而非「discontinue」，用「start」而非「initiate」）。

Knob-agnostic —— 清晰度不可调节，无论CRAFT_LEVEL设置为何，都需运行完整的检查清单。

参考文档：

references/copy.md

（微文案语气与模式）、

references/accessibility.md

（屏幕阅读器的错误提示规范）。

输出格式 —— 审查格式表格：

Before	After	Why

按影响优先级排序（错误提示和破坏性操作优先，其次是CTA，最后是辅助文案）。最后用一段文字总结整体语气风格的转变。如果用户说出「apply」，则编辑代码并重新打印带文件路径的表格。

下一步：

/critique

—— 文案修改会改变层级结构；之后需重新审视界面（rung 1）。