design-system-rules

To ensure UI components meet WCAG 2.2 AA accessibility standards, enforce explicit focus visibility, contrast thresholds, ARIA semantics, and focus management for dynamic interfaces like modals and toasts during implementation.

Stop hardcoded hex, px, and font overrides from breaking your design system by enforcing token-only styling constraints, ensuring all frontend UI changes strictly use design tokens instead of custom values.

Component variant governance in a design system is the practice of forcing reuse of existing components and limiting variation to sanctioned axes like intent, size, density, state, and theme to prevent visual and behavioral fragmentation.

Check responsive behavior and interactive states before implementing a UI component by validating mobile, tablet, and desktop layouts, verifying touch target minimums, and completing state coverage checklists for loading, empty, error, and disabled conditions.

Yes, this design system governance tool works for proposing truly new UI primitives, evaluating whether to select existing components, add sanctioned variants, or introduce new primitives for interactions recurring across product surfaces.

Adding new frontend UI variants causes visual fragmentation when changes drift from established design system rules, bypassing token-only styling constraints and reusing existing components without limiting variation to sanctioned axes.