normalize

Identify feature deviations and align custom styles with design system tokens.

Updated May 15, 2026
One-click install
npx skills add https://github.com/nachopalmeri/agents-system --skill normalize-nachopalmeri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: normalize
Source: https://github.com/nachopalmeri/agents-system/tree/main/.agents/skills/normalize
Command: npx skills add https://github.com/nachopalmeri/agents-system --skill normalize-nachopalmeri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify and fix deviations from the design system, ensuring consistent visuals, tokens, and interaction patterns across features.

Core Features & Use Cases

  • Clarifies where a feature diverges from typography, color, spacing, and component patterns in the design system.
  • Proposes a concrete normalization plan to replace custom styles with design tokens and system components.
  • Supports UX/UI audits by validating accessibility and consistency against established guidelines.

Quick Start

Normalize the current feature to conform to the design system's typography, color palette, spacing, and component patterns.

Frequently Asked Questions about normalize

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

FAQPage Schema
How do I align frontend features with a design system to fix visual inconsistencies?

A design system normalization plan identifies deviations in typography, color, spacing, and component patterns, then replaces custom styles with standard design tokens to ensure visual and interaction consistency across features.

What is a design system normalization plan for UX audits?

A design system normalization plan is a concrete roadmap used during UX audits to replace custom UI styles with established design tokens and system components, ensuring interface consistency and accessibility compliance.

How do I audit UI components for design token compliance?

Audit UI components for design token compliance by validating current implementations against documented patterns, checking typography, color palette, and spacing, and flagging custom styles that diverge from the system.

Do I need documented design tokens to normalize a feature?

Yes, normalizing a feature requires access to documented design tokens, including colors, typography, and spacing, along with established component patterns to successfully replace custom styles.

What's the best way to replace custom styles with design system components?

The best way to replace custom styles is to generate a normalization plan that maps divergent UI elements directly to existing design tokens and documented component patterns within your design system.