adapt
CommandResponsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch…
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.
> /plugin marketplace add educlopez/ui-craft> /plugin install ui-craft@ui-craft
description: 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. argument-hint: "[file or surface path; defaults to current working surface]"
Load the `ui-craft` skill. This command produces findings only — do NOT edit code.
---
Look for `.ui-craft/brief.md`.
---
Run `npx ui-craft-detect` on `$ARGUMENTS` (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.
---
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 close the gap at [category]."
---
Applies only when the target is a complete surface (dashboard, landing, auth, settings shell, portfolio) — skip for single components.
1. **Signature bet present?** Scan for exactly one memorable decision from `references/craft-intent.md` §3 (product / auth / marketing lists). Zero → **Major** ("no signature — surface is competent but anonymous; run `/bolder` or `/polish`"). Two or more competing → **Major** ("signature bets stack — keep the strongest, cut the rest"). 2. **Variance matches surface?** Layout risk visibly inconsistent with the surface's DESIGN_VARIANCE default (e.g. experimental asymmetry on an auth form, or a landing that is one centered symmetric column) → **Major**, unless the brief or spec records the deviation. 3. **Craft Read recorded?** If a `.ui-craft/spec.md` section or session declared a Craft Read, verify the built surface matches it (theme, variance, signature). Mismatch → **Major** with the specific delta.
These findings are Major, never Critical — they gate NOT READY, not BLOCKED.
---
Applies to landings, portfolios, and campaign pages — skip for product shells.
Load `references/recipe-landing.md` and run its Acceptance-bar mechanical checks against the built surface — thresholds (eyebrow count, layout-family budget, hero discipline) live there, not here; this step only names which checks apply and where a violation lands.
1. **Copy self-audit.** Read every visible string (headlines, eyebrows, buttons, captions, alt text, footer). Grammatically broken copy, unclear referents, forced-clever labels ("Field notes" over testimonials, "Quietly trusted by"), or fake-precise numbers with no source → **Major** per `references/copy.md` Copy Self-Audit. 2. **Eyebrow count (mechanical)** — per `references/recipe-landing.md` Eyebrow budget. Over budget → **Major** ("eyebrow flood — delete labels until the count passes"). 3. **Layout-family count (mechanical)** — per `references/recipe-landing.md` Layout-family budget. Any repeat or consecutive-split overrun → **Major**. 4. **CTA intent (mechanical)** — per `references/copy.md` CTAs & Buttons (one label per intent; CTA fits one line at desktop). Violation → **Major**. 5. **Hero discipline** — per `references/recipe-landing.md` Hero discipline. Over budget → **Major**.
---
Load `references/finish-bar.md`. Run all 10 passes in document order. Do not reorder.
**Knob behavior (apply before running):**
**For each pass:**
---
Load `references/review.md` Feedback Hierarchy section.
Group all findings (detector + token + finish-bar) into three tiers:
If any Value findings exist: surface them first in the report and add a standing recommendation to defer all Delight findings until Value findings are resolved. This prevents polish work masking broken functionality.
---
Print this report. Do not add preamble.
## Finalize report — <surface name> **Ship verdict:** READY / NOT READY / BLOCKED > BLOCKED = any Critical finding present. > NOT READY = any Major finding present, no Critical. > READY = zero Critical, zero Major (Minor explicitly accepted). ### Block-ship findings (must fix before merge) - [Pass / detector source] — [finding] — [file:line if available] ### Major findings (fix or defer with recorded reason) - [...] ### Minor findings (polish; ship-okay if explicitly accepted) - [...] ### Deferred per bri
Ship designer-grade UI by default. A design engineering system for AI coding agents — install it as a skill or as the ui-craft CLI, and your agent starts designing like it has taste. Ask for a dashboard, get one you'd put in production.
Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch…
Motion design pass — adds purposeful animations or removes excessive ones, respecting MOTION_INTENSITY and the project's…
Technical UI audit — a11y, performance, responsive. Produces a prioritized findings table.
Amplify personality — raises layout variance and motion, strengthens typography and one signature detail, without slop. Use when…
Write or update the project's durable design brief at .ui-craft/brief.md.
UX copy review across buttons, errors, empty states, and form hints — critiques by default, applies only on request. Use when…
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.