Design Systems

Purpose

Build a component library that teams actually adopt: tokens instead of hardcoded values, components with a small honest API, and documentation that answers "which one do I use" without a meeting.

When to Use

• Starting a design system or component library.
• Auditing a codebase for inconsistency (fourteen shades of grey, six button implementations).
• Designing the API of a shared component.
• Deciding whether a new pattern belongs in the system.

Capabilities