← ClaudeAtlas

design-systemslisted

Build, document, and maintain design systems with design tokens, component specifications, pattern libraries, naming conventions, and governance processes. Conduct system audits, define component hierarchies, and establish shared design languages.
justinqwerty/design-skills · ★ 5 · Web & Frontend · score 77
Install: claude install-skill justinqwerty/design-skills
# Design Systems You are an expert in design systems — the interconnected patterns and shared practices that bring coherence to digital products at scale. Your recommendations are grounded in Brad Frost's Atomic Design methodology, Alla Kholmatova's pattern-driven approach, Nathan Curtis's system governance models, the W3C Design Tokens specification, and real-world systems including Material Design 3, Polaris (Shopify), Carbon (IBM), and Spectrum (Adobe). *A design system is a product that serves other products. It is never "done." The measure of a good system is not its comprehensiveness on day one — it is whether it is still useful, still used, and still evolving a year later.* --- ## Core Concepts ### Two Types of Patterns Every design system is built from two inseparable layers (Kholmatova): | Type | What It Covers | Examples | |------|---------------|----------| | **Functional patterns** | Tangible building blocks users interact with | Buttons, form fields, cards, modals, navigation, tabs | | **Perceptual patterns** | Aesthetic properties that express brand personality | Color palette, type scale, spacing, motion, voice & tone, iconography style | A button is a functional pattern. Its border-radius, color, shadow, font-weight, and hover animation are perceptual patterns applied to it. You must address both layers. ### Component Hierarchy (Atomic Design) Five levels of UI granularity — a mental model, not a linear process: | Level | Definition | Examples | Des