normalize

Normalize UI implementations to match a project's design system.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and removes visual and UX inconsistencies by analyzing a feature and remediating deviations so the UI strictly follows the project's design system, tokens, and component patterns.

Core Features & Use Cases

  • Design system discovery: Locate and interpret style guides, design tokens, and shared UI components used across the repository.
  • Audit and analysis: Detect deviations in typography, color, spacing, components, motion, responsiveness, and accessibility.
  • Normalization plan & execution: Replace hard-coded styles with tokens, swap one-off UI for shared components, align responsive breakpoints, and verify accessibility and interaction patterns.
  • Cleanup and verification: Consolidate reusable pieces into the design system, remove orphaned code, and ensure linting, type-checks, and tests pass after changes.
  • Use case: Convert a bespoke settings page into a design-system-compliant page by replacing custom buttons and spacing with tokenized components and ensuring consistent focus states.

Quick Start

Normalize the specified feature by replacing hard-coded styles with design tokens, substituting custom elements with shared components, aligning spacing and breakpoints to the design system, and running linting and tests to confirm no regressions.

Frequently Asked Questions about normalize

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

FAQPage Schema
How do I refactor UI to use design system tokens instead of hard-coded styles?

Design system normalization refactors UI by replacing hard-coded styles with design tokens, substituting custom controls with shared components, and verifying accessibility, breakpoints, and linting to ensure strict compliance with established project patterns.

What is the best way to audit a feature for design system deviations?

Auditing for design system deviations involves analyzing a feature to detect inconsistencies in typography, color, spacing, motion, responsiveness, and accessibility, then generating a normalization plan to remediate any identified custom or orphaned UI implementations.

Can I use this to fix responsive breakpoints and accessibility on a single page?

Yes, you can normalize a single page or route by aligning responsive breakpoints to the design system, verifying accessibility and interaction patterns, swapping one-off UI elements for shared components, and ensuring type-checks and tests pass after changes.

How do I consolidate orphaned code during a UI refactor?

During a UI refactor, you consolidate reusable pieces back into the design system, remove orphaned code left from deprecated custom elements, and execute code cleanup to ensure linting, type-checks, and tests pass without regressions.

How do I convert a bespoke page into a design-system-compliant page?

To convert a bespoke page into a design-system-compliant page, replace custom buttons and spacing with tokenized components, ensure consistent focus states, align breakpoints, and run linting and tests to confirm no regressions.

Does normalizing UI components require an existing design system in the repository?

Yes, normalizing UI components relies on design system discovery to locate and interpret existing style guides, design tokens, and shared UI components within the repository, ensuring deviations can be accurately detected and remediated.