← ClaudeAtlas

finalizelisted

Pre-ship gate — runs detector, verifies brief and tokens, applies the 10-pass finish bar, ranks findings by feedback hierarchy. Use when the user wants to ship, merge, or finalize a surface and needs a verdict (READY / NOT READY / BLOCKED) before committing. Invoke when the user asks for finalize on their UI, or mentions 'finalize' alongside design / UI / frontend work.
educlopez/ui-craft · ★ 39 · Code & Development · score 83
Install: claude install-skill educlopez/ui-craft
<!-- AUTO-GENERATED. Do not edit here. Source: skills/ui-craft/ + commands/*.md. Regenerate with `node scripts/sync-harnesses.mjs`. --> **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. Load the `ui-craft` skill. This command produces findings only — do NOT edit code. --- ## Step 1 — Brief check (gate) Look for `.ui-craft/brief.md`. - Absent: STOP. Output: "No brief found. Run `/brief` first. `/finalize` requires a design brief to distinguish intentional decisions from findings." Do not proceed. - Present: load it. Extract principles (numbered, in conflict-resolution order). These are the override registry for Steps 4–5. --- ## Step 2 — Detector Run `npx ui-craft-detect` on the target the user described (or current working surface if no argument). Capture all output. Every Critical detector finding maps directly to a block-ship finding in the report. Preserve detector source labels. --- ## Step 3 — Token check Quick three-question audit (no deep read required): 1. Are all three token layers present (primitives → semantic → component)? 2. Are both light and dark modes explicitly authored (not inverted)? 3. Are all seven token categories represented (color, spacing, radius, shadow, typography, motion, z-index)? Any "no": flag as Major. Do not block ship. Append a recommendation: "Run `/tokens` to clo