normalize

To align a page with your design system, this Skill analyzes typography, color, spacing, components, and motion to identify deviations, then creates and executes a normalization plan that ensures strict UI consistency and accessibility compliance.

The best way to fix UI inconsistencies is to normalize the feature by replacing custom styles like non-standard buttons with predefined design system components, ensuring a unified look and feel across the application.

To standardize typography and spacing against a style guide, this Skill discovers your design system documentation, analyzes current feature deviations, and systematically redesigns elements to match system tokens and standards.

Yes, normalizing frontend components requires existing design system documentation. The process involves discovering these predefined design principles and tokens to accurately analyze deviations and execute systematic alignment changes.

Yes, you can use this to clean up obsolete code. The normalization process includes executing systematic changes to replace custom styles with standard components and subsequently removing the redundant obsolete code.

You should not use a design system normalization process when building experimental prototypes or highly custom interfaces that intentionally deviate from established design tokens, as it strictly enforces predefined component standardization and UI alignment.