normalize

Audit and realign UI components to design system tokens and patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ChoonwooLim/SodamFN --skill normalize-choonwoolim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: normalize
Source: https://github.com/ChoonwooLim/SodamFN/tree/main/.claude/skills/normalize
Command: npx skills add https://github.com/ChoonwooLim/SodamFN --skill normalize-choonwoolim

SYSTEM DOCUMENTATION & REQUIREMENTS

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

  • Design system alignment: identify and fix spacing, typography, tokens, and component usage to conform to the design system.
  • Token-driven normalization: replace hard-coded values with tokens and design system primitives.
  • Use Case: When a feature drifts from the design system, restore alignment across pages, routes, and components.

Quick Start

Normalize a feature to align it with the design system using design tokens and established patterns.

Frequently Asked Questions about normalize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix UI design drift and align components with design tokens?

To fix UI design drift, you audit and realign components to adhere to design system tokens, spacing, and patterns. This process replaces hard-coded values with tokens to ensure consistency across pages and routes.

What is design token normalization for UI components?

Design token normalization is the process of auditing UI components to replace mismatched, one-off styles with defined design system tokens. It corrects typography and spacing drift to restore visual consistency.

How do I replace hard-coded spacing values with design system tokens?

You replace hard-coded spacing values by conducting a UI audit to identify drift, then applying token-driven normalization. This ensures all components use design system primitives instead of custom, one-off styles.

Do I need design system documentation to normalize UI spacing and typography?

Yes, normalizing UI spacing and typography requires access to design system documentation and token definitions. This context is necessary to accurately identify drift and apply the correct design tokens.

When should I run a UI audit for design system consistency?

You should run a UI audit for design system consistency when you notice mismatched styles, typography drift, or spacing inconsistencies across features. It brings out-of-sync components back in line with established guidelines.

What's the best way to audit a feature for design system alignment?

The best way to audit a feature for design system alignment is to use a context gathering protocol to review pages and components. This identifies hard-coded values and realigns them with established design tokens and patterns.