208 cards
A design system is a shared set of principles, components, patterns, and rules that helps teams build consistent products faster. It exists because individual product teams repeatedly face the same design and engineering decisions, and a system provides reusable answers to those questions. The benefit compounds at scal...
A good design system rests on a small set of guiding principles that every team can repeat and apply. The most practical principle is to make the right choice the easiest choice: when system usage is frictionless, adoption follows without enforcement. Other principles like "real usage beats catalog breadth" or "designe...
Design tokens are named values for color, spacing, typography, and other primitives that can be reused across tools and code. They are the atomic layer of a system: instead of writing a hex value in twenty places, the system exposes a token that resolves to that value everywhere. This abstraction is what makes consiste...
Atomic design, proposed by Brad Frost, gives teams a shared vocabulary for thinking about UI composition. Atoms are the smallest UI building blocks: a button, input, icon, or single token, not useful alone but combined into molecules. Molecules are small groups of atoms that work as a single unit, such as a labeled inp...
Accessibility should be built into a design system from the start so that every team inherits better behavior instead of fixing the same issues repeatedly. The shorthand a11y refers to the eleven characters between the first "a" and the "y" in the word. The international standard is the Web Content Accessibility Guidel...
Documentation is the surface through which consumers actually experience the system. Component documentation explains when to use a component, how it behaves, and what variants or constraints apply. Examples are essential because they show teams how to apply abstract guidance correctly in real interfaces, and anti-patt...
System adoption is the degree to which product teams actually use the design system in day-to-day work, and it is the most honest measure of value. Adoption often fails when the system is hard to use, poorly documented, or disconnected from product reality, when using it is slower or more painful than going around it....