design-systems

Design Systems helps teams decide whether to build a design system and then scale it, drawing on frameworks from four product leaders who have shipped design systems at companies such as Figma and Airbnb. It applies when someone is creating a component library, establishing design tokens, scaling brand consistency, or weighing whether they are at the right stage to invest in a system at all.

The approach starts by assessing the underlying need - consistency, speed, or both - and clarifying scope across three possible deliverables: a component library, design tokens, and documentation. From there it emphasizes designing for adoption so that non-designers can use the system correctly, and planning for how the system will be maintained and evolved rather than treated as finished. Several principles anchor the guidance: separating concept from production by locking down low-fidelity 'block frames' before applying the system for fast high-fidelity output; recognizing that design systems are a driver of enterprise expansion and internal champions for scaling; designing assets that teach their own correct usage through inherent structure; and an observation that interface design is shifting away from flat aesthetics toward more dimensional, tactile, AI-enhanced experiences.

The skill also coaches users with diagnostic questions - the biggest inconsistency problem, who will use the system, how adoption and success will be measured, whether resources exist to maintain it, and what the smallest viable first version looks like. It flags recurring mistakes: building too early before enough patterns exist, over-engineering systems that only expert designers can use, shipping without dedicated ownership, ignoring adoption, and treating the system as static. A references file collects the four guest insights, and a related skill covers running design reviews.