- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add educlopez/ui-craft --skill polish -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add educlopez/ui-craft --skill polish -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add educlopez/ui-craft --skill polish -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add educlopez/ui-craft --skill polish -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/educlopez/ui-craft/tree/HEAD/.agents/skills/polishDel publicador
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).
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 functional
---name: polishdescription: Final craft pass applying the compound details from the polish checklist — micro-typography, spacing rhythm…---# .agents/skills/polish/SKILL.mdResumen general
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.
Preguntas frecuentes
Descarga .agents/skills/polish/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/educlopez/ui-craft.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.