normalize

Normalize frontend UI features by replacing hard-coded values with design tokens.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/Tea-4-Life/Tea4Life-Frontend-Website --skill normalize-tea-4-life
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: normalize
Source: https://github.com/Tea-4-Life/Tea4Life-Frontend-Website/tree/main/.agents/skills/normalize
Command: npx skills add https://github.com/Tea-4-Life/Tea4Life-Frontend-Website --skill normalize-tea-4-life

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize design to match your design system and ensure consistency across UI, reducing visual drift and fragmentation across features.

Core Features & Use Cases

  • Design token alignment: replace hard-coded values with token-based styles to ensure cohesive visuals.
  • Component harmonization: consolidate custom UI into design-system components or patterns.
  • Accessibility checks: enforce contrast, focus states, and keyboard navigation in line with tokens.

Quick Start

Normalize a UI feature by applying design tokens and replacing bespoke styles with system components in your frontend workflow.

Frequently Asked Questions about normalize

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

FAQPage Schema
How do I normalize a UI feature to match my design system?

Design token alignment replaces hard-coded values with token-based styles for typography, color, and spacing. This mechanism ensures cohesive visuals across platforms by enforcing consistent component usage and eliminating visual drift in frontend features.

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

Replace hard-coded values by applying design token alignment to your frontend workflow. Gather context on your UI feature, swap bespoke styles for system components, and validate contrast, focus states, and keyboard navigation for accessibility compliance.

Does design token normalization handle accessibility checks?

Yes, design token normalization includes accessibility checks to enforce contrast, focus states, and keyboard navigation. Applying token-based styles ensures that UI features meet accessibility requirements while maintaining visual consistency across platforms.

When do I need to normalize UI component usage across platforms?

You need to normalize UI component usage across platforms when visual drift and fragmentation appear in your features. Replacing bespoke styles with design-system components ensures cohesive typography, color, and spacing consistency throughout your organization.

What's the best way to consolidate custom UI into design-system components?

The best way to consolidate custom UI is through component harmonization during the normalization process. Follow the Context Gathering Protocol to map bespoke styles, replace them with design tokens, and validate responsive behavior across platforms.