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.