normalize

Design system normalization refactors divergent UI into consistent patterns by applying established tokens for typography, color, and spacing. It is needed when a feature's UI drifts from design guidelines, ensuring uniform aesthetics and behavior across pages.

To fix visual drift and enforce UI consistency, direct the system to normalize the target feature against design system standards. This process applies token-based styling and component reuse, automatically reporting any deviations from the established guidelines.

Yes, standardizing UI features to a design system includes accessibility considerations and conformance checks. Normalization satisfies a11y constraints by enforcing token-based styling and component reuse across all refactored pages and features.

Yes, you can use design tokens to refactor divergent UI components. Normalization aligns typography, colors, and spacing with your established design tokens, converting inconsistent feature UIs into reusable, conformant component patterns.

The limitation of normalizing UI to design system tokens is that it relies entirely on the pre-existing design system definitions. If the established tokens, typography, or component patterns are incomplete, normalization can only align features to those current constraints.