normalize

To fix design drift, you audit and realign UI components to conform to design system tokens, spacing, and patterns. This process replaces bespoke styles with standardized tokens to achieve consistent typography, color, spacing, and accessibility alignment across your project.

UI normalization is the process of auditing user interface components and replacing mismatched styles with design system tokens. It ensures features comply with established standards for typography, color, spacing, accessibility, and responsive behavior across all pages and routes.

You audit UI for token mismatches by evaluating features against design system tokens and accessibility patterns. A normalization plan identifies bespoke styles, replaces them with system components, and ensures proper responsive behavior alignment.

Yes, you must gather design context before normalizing UI components. If no design context exists, you need to run a teaching protocol first to establish the design principles, anti-patterns, and tokens required for the realignment process.

The best way to consolidate reusable code after realigning UI to design tokens is to remove obsolete bespoke styles, consolidate reusable pieces, and run lint and type checks. This ensures design consistency and maintains a clean token-based architecture across the project.

You should normalize UI components instead of rebuilding when users mention consistency, design drift, mismatched styles, or token violations. Normalization efficiently brings existing features back in line with the design system without requiring a full functional rewrite.