normalize

Align UI features to design system tokens, typography, color, and spacing.

2.4k|295|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/The-Vibe-Company/companion --skill normalize-the-vibe-company
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: normalize
Source: https://github.com/The-Vibe-Company/companion/tree/main/archived/legacy-companion/.agents/skills/normalize
Command: npx skills add https://github.com/The-Vibe-Company/companion --skill normalize-the-vibe-company

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize design to match your design system and ensure consistency across features and interfaces, reducing visual drift and inconsistencies for teams.

Core Features & Use Cases

  • Design-system alignment: Conforms typography, colors, spacing, tokens, and components to the established system.
  • Accessibility & quality checks: Verifies contrast, focus states, and pattern consistency across pages.
  • Use case: Apply to a new feature page or route to bring it into alignment with tokens and patterns before launch.

Quick Start

Run the normalization workflow on the target page or component to align it with the design system.

Frequently Asked Questions about normalize

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

FAQPage Schema
How do I align UI components with an existing design system?

Run a normalization workflow on your target page or component to align typography, colors, spacing, and tokens with the established design system. This process ensures consistency across features and reduces visual drift for teams.

What is design system normalization and when do I need it?

Design system normalization is the process of conforming typography, colors, spacing, and components to established guidelines to reduce visual drift. You need it when a new feature page or route requires alignment with tokens and patterns before launch.

How do I check accessibility and contrast when applying design tokens?

Verify accessibility and contrast by checking focus states and pattern consistency across pages. Document token usage and verify changes through linting and visual QA before deployment to ensure quality.

Can I apply a normalization workflow to an entire feature route before launch?

Yes, you can apply the normalization workflow to an entire feature page or route to bring it into alignment with design tokens and patterns. This ensures the interface matches the established system consistently before launch.

What's the best way to fix visual drift and inconsistencies across UI features?

Fix visual drift by conforming typography, colors, spacing, tokens, and components to the established design system. Apply the normalization workflow to pages and components to ensure consistency across interfaces for teams.

Do I need to run linting and visual QA after normalizing design tokens?

Yes, you need to verify changes through linting and visual QA before deployment. Documenting token usage and verifying changes ensures the UI maintains accessibility, contrast, and pattern consistency across the application.