Conciseness

The body is pure imperative rules with zero padding — e.g., "NEVER use `h-screen`, use `h-dvh`" and "MUST use `text-balance` for headings and `text-pretty` for body/paragraphs" — and explains nothing Claude already knows. Every token earns its place.

Actionability

Guidance is highly concrete: specific classes (`h-dvh`, `tabular-nums`, `size-*`), libraries (`motion/react`, `cn`), thresholds ("NEVER exceed `200ms`"), commands (`pnpm lint`, `pnpm test`, `pnpm build`, `pnpm verify`), and a defined review output format (violation + why + fix). Minor gaps keep it below fully executable: the "fixed `z-index` scale" is never specified and there are no copy-paste code examples.

Workflow Clarity

Both usage modes are unambiguous (apply constraints to UI work; for review, output violations with snippet + fix) and the Verify section provides explicit commands with a GO/NO-GO checkpoint. It falls short of a 5 because there is no error-recovery loop (what to do on NO-GO) and the body is longer than the simple-skill threshold.

Progressive Disclosure

No bundle files exist and the ~84 lines of rules are appropriately inline under clear section headers (Stack, Components, Interaction, Animation, Typography, Layout, Performance, Design), with one clearly signaled external link to Base UI. Minor gaps — e.g., the unspecified z-index scale and 'Source: ui-skills.com' attribution — keep it from a 5, and the under-50-line simple-skill exception does not apply.

Specificity

"Baseline UI rules to prevent design slop" names the domain but lists no concrete actions or capabilities, matching 'Names the domain but actions are minimal or generic'. It is not a 3 because no specific actions (e.g., apply constraints, review files for violations) are actually enumerated.

Completeness

Both parts are present: 'what' ("Baseline UI rules to prevent design slop") and an explicit 'when' ("Use for UI design or review"), but the 'when' is broad and could be more specific. It is not a 5 because the trigger guidance lacks concrete trigger phrases, and not a 3 because an explicit 'Use for...' clause exists.

Trigger Term Quality

"Use for UI design or review" includes the natural phrase 'UI design', but common variations users would say — frontend, interface, components, styling, Tailwind — are missing. Good keyword coverage is not reached, so it sits at 'some relevant keywords but missing common variations'.

Distinctiveness Conflict Risk

"prevent design slop" carves a recognizable niche, but "Use for UI design or review" is broad and would overlap with general frontend, styling, and design-review skills. This matches 'Somewhat specific but could still overlap with similar skills'.