Ux framework

Skill TarekAwwad/claude-ux-framework/skills/ux-framework

Use when creating or modifying any web UI (pages, dashboards, navigation, multi-screen features) or when asked to review/audit an app's UX. Enforces a UX pass before UI code and provides audit checklists. Not for single-component styling tweaks.From its SKILL.md

Install

npx -y skills add TarekAwwad/claude-ux-framework --skill ux-framework

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 389 tokens by cl100k_base, as published. Nobody here has run it

ux-framework

UIs must be designed around what the user is trying to do, then built. This skill enforces that order.

Hard rules

No UI code before a written UX spec exists (templates/ux-spec.md). Scale it down for small features; never skip it.
Every view handles all five states: empty, loading, error, partial, ideal.
Every screen answers: what is the one thing the user does here?
Do not declare UI work done before the self-audit (step 4 below).

Build mode

UX pass: copy templates/ux-spec.md, fill every section, show the user.
Load references by the routing table below.
Build, following references/principles.md plus the routed module.
Self-audit with references/audit-checklist.md; fix or explicitly justify every failed check before declaring done.

Audit mode

When asked to review/audit UX: follow "How to run an audit" in references/audit-checklist.md. Deliver findings in its report format.

Routing table

Work involves	Also load
dashboard, analytics, monitoring, reports, charts, KPIs	references/dashboards.md
app shell, nav, sidebar, menu, IA, new pages, multi-screen flows	references/navigation.md
anything else UI	references/principles.md only

references/principles.md is always loaded in build mode.

Boundaries

Visual aesthetics (typography, color, personality): defer to a frontend-design skill if available.
Chart styling and palettes: defer to a dataviz skill if available; chart SELECTION rules stay here (references/dashboards.md).
This skill owns: structure, flows, states, IA, hierarchy, density.