name: polish
description: "Final craft pass applying the compound details from the polish checklist — micro-typography, spacing rhythm, hover states, and a signature detail — directly to code. Use when the surface is functionally complete but feels unfinished, or when the user says "polish this" / "it looks generic" / "add the final touches". Invoke when the user asks for polish on their UI, or mentions 'polish' alongside design / UI / frontend work."
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 the target the user described. 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.
