polish

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.

Polish the UI at

$ARGUMENTS

. Load the

ui-craft

skill.

Source of truth: read

references/review.md

→ Polish Pass (Compound Details) section. Apply every item on that list to the target. Do not re-derive the list here —

review.md

owns it.

Then the signature detail: surfaces built via

/craft

already carry exactly one signature bet, chosen in the Craft Read and built in the first pass (

references/craft-intent.md

). Polish verifies it survived and strengthens it — never stacks a second. Only if the surface predates craft-intent (no signature anywhere) do you propose and add one: a subtle motif, an asymmetric layout break, a custom list marker, a distinctive hover — one thing someone would remember.

Knob gating (CRAFT_LEVEL):

```
≤ 4
```
→ skip the Polish Pass. Ask the user first before running it.
```
5-7
```
→ apply everything on the list, leave the signature as-built unless asked.
```
8+
```
→ apply everything + verify/strengthen the signature detail (add one only if the surface has none).

Output: edit the code directly (polish is implementation, not critique). After each file, print the Review Format table from SKILL.md showing what changed and why. No full diffs — one row per change.

Close every run with a Craft Report (

references/review.md

→ Craft Report). The table above is the per-file diff log; the Craft Report is the run's receipt — Checked / Passed / Changed / Left alone / Verdict. Produce it even when the Polish Pass found nothing to change — that is itself the finding.

Next step:

/finalize

— the pre-ship gate (rung 3).

背景说明：此子技能是更广泛的

ui-craft

技能的一个细分模块。如果已安装

ui-craft

技能，请先阅读其SKILL.md中的发现环节（Discovery）、防冗余环节（Anti-Slop）和工艺测试环节（Craft Test），再应用以下具体模块。

对

$ARGUMENTS

指向的UI进行优化。加载

ui-craft

技能。

权威参考：阅读

references/review.md

→ **优化阶段（复合细节）**章节。将该列表中的所有项应用到目标对象上。请勿在此重新推导列表——

review.md

为唯一权威来源。

标志性细节处理：通过

/craft

构建的界面已包含一个明确的标志性设计决策，该决策在Craft Read环节选定，并在第一阶段构建完成（详见

references/craft-intent.md

）。优化阶段需确认该细节仍存在并强化它——绝不能添加第二个。只有当界面早于craft-intent（无任何标志性细节）时，才需提出并添加一个：比如一个微妙的主题图案、一处不对称的布局突破、一个自定义列表标记、一种独特的悬停效果——一个让人印象深刻的细节。

等级控制（CRAFT_LEVEL）：

```
≤ 4
```
→ 跳过优化阶段。运行前需先询问用户。
```
5-7
```
→ 应用列表中的所有内容，除非用户要求，否则保留原有的标志性细节。
```
8+
```
→ 应用所有内容 + 确认/强化标志性细节（仅当界面无标志性细节时添加一个）。

输出要求：直接编辑代码（优化是实现环节，而非评审）。每编辑一个文件后，打印SKILL.md中的评审格式表格，展示变更内容及原因。无需完整差异对比——每项变更占一行。

每次运行结束时生成工艺报告（Craft Report）（详见

references/review.md

→ Craft Report）。上述表格是每个文件的变更日志；工艺报告是本次运行的结果凭证——包含已检查/已通过/已变更/未改动/结论。即使优化阶段未发现任何需要变更的内容，也需生成报告——这本身就是一项结果。

下一步：

/finalize

——发布前的最后检查环节（第3阶段）。