How do I install the Polish skill?

Run npx skillmds@latest add educlopez/polish in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Polish safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Polish?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Polish free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Polish?

educlopez (@educlopez) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Polish by educlopez — Agent Skill

Name: Polish
Rating: 4.666666666666667 (3 reviews)
Author: educlopez

Polish

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.

educlopez b5d8b94 2.4 KB Updated Sep 9, 2026

File contents

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).

---name: polishdescription: 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 `$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).

Frequently asked questions