Measure gaps in the current design-system primitives, derive values from the project’s own visual vocabulary, and fill only the missing declarations after review.
Where: Design System → Fill Design System, or AI/MCP → complete_design_system
Key ideas
- Completes; it does not replace: The operation targets missing primitive coverage and preserves already declared design-system values.
- Project-attributed values: Colors, type, spacing, radii, shadows, and other supported primitives are derived from the current document rather than a generic preset.
- Plan and confirmation: The first call reports how many tokens/class rules would be created and what is held back; only a confirmed second call writes.
Steps
- Inspect the current design tokens/primitives and identify real gaps.
- Run Fill Design System without confirmation to generate a plan.
- Review proposed token/rule counts and held-back items.
- Confirm to write, then inspect the Design System and representative pages.
Tips
- Run this before extracting/applying other design-system classes so existing declarations do not cause useful values to be held back.
- Do not fill primitives merely to increase coverage; keep only values the product actually uses.
Limitations and important notes
- If the project already declares everything supported, the tool reports nothing to fill and should not be confirmed again.