normalize

Audits UI and aligns typography, spacing tokens, and patterns to design system standards.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Fldicoahkiin/SYNCHRONICITY_Route_Planner --skill normalize-fldicoahkiin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: normalize
Source: https://github.com/Fldicoahkiin/SYNCHRONICITY_Route_Planner/tree/main/.agents/skills/normalize
Command: npx skills add https://github.com/Fldicoahkiin/SYNCHRONICITY_Route_Planner --skill normalize-fldicoahkiin

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

  • Normalization planning: Define concrete changes to align typography, color tokens, spacing, and component usage with the design system.
  • Pattern enforcement: Replace or update custom styles with design-system tokens and components to ensure consistency across pages.
  • Use Case: Imagine a new feature page that drifts from typography scales; this skill brings it back in line with tokens and patterns.

Quick Start

Review the current UI and implement a normalization plan to align typography, spacing, and components.

Frequently Asked Questions about normalize

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

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

UI normalization is the process of auditing and realigning user interfaces to replace mismatched styles and hard-coded values with standardized design system tokens, enforcing consistent typography, spacing, and component patterns across all pages.

Can I use this to audit component patterns and spacing tokens across an entire feature page?

Yes, you can audit any UI feature, page, route, or component to check spacing tokens, typography scales, and component patterns, applying a normalization plan to bring everything back into design-system conformance.

What is the best way to replace hard-coded values with design system component patterns?

The best way is to perform a UI audit to identify custom styles and hard-coded values, then create a normalization plan that replaces them with design-system tokens and standard component patterns for consistency.

Does UI normalization help with accessibility conformance as well as typography and color tokens?

Yes, UI normalization satisfies design-system conformance requirements that include typography, color tokens, spacing, component patterns, and accessibility, ensuring comprehensive UI consistency across the application.

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

You should run a UI audit for design system consistency whenever a new feature page drifts from typography scales, when you notice mismatched styles, or when a component needs a refresh to align with tokens and patterns.