← ClaudeAtlas

ui-ux-designlisted

Use for frontend UI/UX: read-only review (default — visual, accessibility, responsive, interaction) or authorised design, redesign, and live iteration. Not for source-diff review or React profiling; use code-review or react-performance.
mblauberg/provenant · ★ 2 · Web & Frontend · score 68
Install: claude install-skill mblauberg/provenant
<!-- Modified from Impeccable for this harness; see the repository THIRD_PARTY_NOTICES.md. --> # UI/UX design Review or design production-grade frontend interfaces. Two branches share one entry point; the model picks the branch from what the request authorises, never a slash command. ## Branches - **review** (default, read-only). Evidence-bearing critique of the rendered UI: visual hierarchy, accessibility, responsiveness, interaction states, copy and brand fit. No `Write`/`Edit`/`NotebookEdit` calls. Load [review](reference/review.md). - **design/make** (write authority required). Design, implement, redesign or polish an interface, including the interactive `live` codegen protocol. Load [setup](reference/setup.md), then [command routing](reference/command-routing.md); for live browser work, [live](reference/live.md). A request framed as review stays on the review branch even when a fix looks obvious; escalate to design/make only under an explicit authority grant naming `implement` (or this skill under `implement`) as action-owner. Never infer write authority from review findings alone. ## Lifecycle boundary This skill supplies the frontend review and design methods; it is not a delivery lifecycle. Run every source-changing command inside `implement`. Route unsettled design intent through `scope`, design-document placement through `engineering-docs`, general source-diff review through `code-review`, and measured React performance work through `react-perfo