You Don't Have a Design System
The difference between parts (components) and form (structure)
- Even when the same component library (Base UI) and design tokens are used, each development team or AI agent may compose screens with different patterns, such as card layouts, tabs, autosave versus explicit Save buttons, and so on.
- The problem is not a defect in the UI parts, but the absence of clear rules and decisions about structural arrangement and behavior patterns.
The role of a true design system
- Beyond simply supplying components, the core role of a true design system is to standardize recurring design decisions—structure, layout, and interaction rules—and make them reusable.
- The stages of Atomic Design should be applied to clearly define rules for layout and behavior:
- Atoms: buttons, switches, input fields
- Molecules: validated input fields, switches with confirmation flows
- Organisms: setting rows that combine label, description, and control
- Template: a full page frame with consistent scope and order, such as SettingsFrame
The effect of applying clear rules
- Unlike simply giving AI agents components, only when page composition rules, layout standards, and interaction guidelines such as autosave and Danger zone placement constraints were explicitly provided did the results become unified and consistent across the product.
A true design system is not a “library that provides parts,” but a “system that standardizes and guides recurring decisions.”
