Analyze and redesign the feature to perfectly match our design system standards, aesthetics, and established patterns.

Normalization is not just visual cleanup. It is restoring the feature to the system so spacing, type, color, interaction, and hierarchy all speak the same language again.

Consult the design-system alignment reference for tokens vs components vs patterns, drift, and when to normalize locally versus escalate to system work. Consult the interaction design reference when normalization includes restoring familiar patterns, improving target sizing, or removing bespoke interaction behavior from standard controls. Consult the legacy modernization reference when the feature lives inside a legacy system, mixed old/new flow, or partial migration where low-risk upgrade strategy matters as much as visual alignment.

MANDATORY PREPARATION

Read frontend-design and follow its Context Gathering Protocol. Reuse available context and ask only about consequential gaps.

Resolve the owning application's system with project context. When documentation and implementation disagree, identify which represents the requested target before changing either. Verify relevant changes with visual verification.

Plan

Before making changes, deeply understand the context: