normalize

SKILL.md

Analyze and redesign features to match your design system standards and ensure consistency.

Requires upfront design system discovery—searches for documentation, UI guidelines, and design tokens before making changes; asks clarifying questions rather than guessing at principles

Systematically normalizes typography, color, spacing, components, motion, responsive behavior, and accessibility across eight key dimensions

Prioritizes UX consistency and usability over visual polish; replaces custom implementations with design system equivalents and removes hard-coded values in favor of design tokens

Includes cleanup phase to consolidate reusable components, remove orphaned code, and verify quality against repository standards

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

MANDATORY PREPARATION

Invoke /impeccable — 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 /impeccable teach first.

Plan

Before making changes, deeply understand the context:

Discover the design system: Search for design system documentation, UI guidelines, component libraries, or style guides (grep for "design system", "ui guide", "style guide", etc.). Study it thoroughly until you understand:

Core design principles and aesthetic direction

Target audience and personas

Component patterns and conventions

Design tokens (colors, typography, spacing)

CRITICAL: If something isn't clear, ask. Don't guess at design system principles.