What problem does it solve?
Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
Core Features & Use Cases
- Mandatory preparation: Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.
- Plan: Deeply understand the context by discovering the design system, analyzing the current feature, and creating a normalization plan.
- Execute: Address typography, color & theme, spacing & layout, components, motion & interaction, responsive behavior, accessibility, and progressive disclosure.
- Clean Up: Consolidate reusable components, remove obsolete code, verify quality, and ensure DRYness.
- Never: Do not create new one-off components when design system equivalents exist, do not hard-code values that should use tokens, do not introduce patterns that diverge from the design system, and do not compromise accessibility for visual consistency.
Quick Start
Run the design-system normalization workflow on the target feature by performing the mandatory preparation and then executing the Plan, Execute, and Clean Up steps.
