ux-atomic-design

Classifies interface components into Brad Frost's five-level Atomic Design taxonomy with token audits and Storybook coverage reports.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/geekatron/jerry-claude-plugin --skill ux-atomic-design-geekatron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-atomic-design
Source: https://github.com/geekatron/jerry-claude-plugin/tree/main/skills/ux-atomic-design
Command: npx skills add https://github.com/geekatron/jerry-claude-plugin --skill ux-atomic-design-geekatron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design systems built ad hoc accumulate duplicate components, inconsistent design tokens, and undocumented Storybook stories. This sub-skill structures component libraries into a systematic hierarchy so teams can audit consistency, find consolidation opportunities, and measure documentation coverage. ## Core Features & Use Cases - 5-Level Component Taxonomy: Classifies UI elements into Atoms, Molecules, Organisms, Templates, and Pages with deterministic boundary adjudication rules. - Design Token Auditing: Measures token drift ratios across seven categories (color, typography, spacing, breakpoints, elevation, border, motion) with PASS/FAIL thresholds. - Storybook Coverage & Consolidation Analysis: Reports component, state, and variant coverage per hierarchy level and identifies duplicate components for merging. - Use Case: A team refactoring a checkout flow asks the ux-orchestrator to inventory its components; this sub-skill produces a classified inventory, token drift report, and prioritized consolidation roadmap handed off to inclusive design evaluation. ## Quick Start Ask the /user-experience parent skill to build an atomic design inventory for your component library, and the ux-orchestrator will route the request to this sub-skill.

Frequently Asked Questions about ux-atomic-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify components using atomic design methodology?▼

Classify bottom-up: identify atoms first (single-function elements like buttons and inputs), then molecules (2-5 atoms serving one purpose), then organisms (recognizable sections with layout logic), templates, and pages. Ambiguous molecule/organism boundaries are resolved with a five-step adjudication procedure.

What is design token drift and how is it measured?▼

Token drift occurs when components use hardcoded style values instead of design token references. It is measured as drift_ratio = hardcoded_values / total_style_values per token category, with a ratio above 0.20 flagged as a FAIL indicating lost token governance.

Does this skill work without a Storybook instance?▼

Yes, it falls back to Manual Component Inventory Mode when the Storybook MCP adapter is unavailable. In degraded mode, coverage percentages and token audits rely on user-provided inventory data, and the output discloses reduced accuracy per P-022.

When should I use atomic design versus heuristic evaluation?▼

Use atomic design to structure and classify components into a hierarchy; use heuristic evaluation (/ux-heuristic-eval) to assess usability quality against Nielsen's 10 heuristics. Atomic design produces the component inventory that downstream accessibility evaluation consumes.

What are the Storybook coverage targets for a design system?▼

Component coverage targets are 80% for atoms and 60% for molecules/organisms; state coverage targets are 70% and 50%; variant coverage targets are 60% and 40%. These are framework-internal heuristics adjustable to team maturity.