How to decide what belongs in a design system
By Rosario Meza
What is a design system?
A design system is a shared set of design decisions, reusable components, and guidelines for building a product. It defines foundations like color, type, and spacing, and shows how to use components like buttons, form fields, and status chips. Designers and developers use it to make the same patterns look and behave consistently across screens.
Color
Typography
Heading
Body text
Spacing
When I see the same pattern on two screens, I check what it does in each place. A “Needs review” chip in a request table and the same chip on the request detail page both tell someone the current status. If clicking a similar-looking chip changes the results in a table, that interaction comes with a different set of requirements. That distinction helps me decide what belongs in the library.
Reuse the component when it does the same job
A request’s status should be recognizable in the table and on its detail page. Use the same status chip in both places. If a second workflow needs a label such as “Awaiting documents” with a tone the chip already supports, use the existing instance and change its text. Check that a longer label still fits in the narrowest layout where it will appear.
Add a variant for a recurring difference
Suppose several workflows need to distinguish a blocked request from one awaiting routine review. If the existing status styles don’t cover that distinction, add a variant for the new tone. Keep the same spacing and text treatment, and document when to use it. The label should still communicate the status on its own.
Create a component when the interaction changes
An active filter chip might show “Needs review” with a control that removes the filter. It needs a keyboard focus state, a clear name such as “Remove Needs review filter,” and defined behavior when it’s removed. If that pattern recurs across tables, give it its own component. It can share the status chip’s spacing and shape tokens while documenting its own behavior.
Reuse
Add a variant
Create a filter chip
Includes a remove control
A checklist before publishing to the Figma library
- Search the library and compare the existing component’s purpose and behavior.
- Check the pattern in two real layouts. If it only serves one screen, keep it local while the design settles.
- Use a text property for the label and reserve variants for supported, repeatable differences.
- Check long labels, contrast, and keyboard behavior for interactive components.
- Add an example and review the component’s properties and behavior with engineering.