normalize

Normalize frontend UI components to align with design-system tokens and patterns.

4|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Tresillo2017/zephyron --skill normalize-tresillo2017
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: normalize
Source: https://github.com/Tresillo2017/zephyron/tree/main/.agents/skills/normalize
Command: npx skills add https://github.com/Tresillo2017/zephyron --skill normalize-tresillo2017

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize design to match your design system and ensure consistency across UI components and patterns.

Core Features & Use Cases

  • Align UI components with tokens and patterns from the design system.
  • Identify and fix deviations from typography, color, spacing, and components across features.
  • Use case: when introducing a new feature, ensure it adheres to system principles before integration.

Quick Start

Gather design-system context and apply tokens, components, and patterns to normalize the feature.

Frequently Asked Questions about normalize

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

FAQPage Schema
How do I normalize UI designs to match an existing design system?

To normalize UI designs to a design system, you align typography, color, spacing, and components with established tokens and patterns. This process enforces design-token usage and component conventions to ensure frontend UI consistency across features.

What is design token usage and how does it enforce UI consistency?

Design token usage is the practice of applying standardized variables for typography, color, and spacing across frontend features. It enforces UI consistency by replacing hardcoded values with design-system tokens and component conventions.

How do I fix UI deviations from typography and spacing rules before feature integration?

To fix UI deviations from typography and spacing rules, you identify mismatches across features and apply documented normalization plan criteria. This ensures new features adhere to system principles and design tokens before integration.

Does normalizing frontend UI require accessibility guidelines and component conventions?

Yes, normalizing frontend UI requires accessibility guidelines and component conventions. The process targets frontend UI work across features to ensure typography, color, and spacing align with tokens and patterns while meeting accessibility standards.

What's the best way to document a design system normalization plan for frontend components?

The best way to document a design system normalization plan is to define required technical criteria that enforce design-token usage, component conventions, and accessibility guidelines. This plan guides the alignment of UI components before integration.