normalize

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/FairladyZ625/Obsidian-Brain-OS --skill normalize-fairladyz625
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: normalize
Source: https://github.com/FairladyZ625/Obsidian-Brain-OS/tree/main/skills/recommended/normalize
Command: npx skills add https://github.com/FairladyZ625/Obsidian-Brain-OS --skill normalize-fairladyz625

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize design implementations to remove one-off styles, visual drift, and accessibility regressions by aligning features with an established design system and shared tokens.

Core Features & Use Cases

  • Design discovery & context gathering: Search and synthesize design system documentation, design tokens, component libraries, and UX patterns to form a clear normalization baseline.
  • Audit and analysis: Identify deviations in typography, color, spacing, components, motion, responsive behavior, and accessibility; distinguish cosmetic issues from functional mismatches.
  • Normalization planning and execution: Replace custom components with design system equivalents, swap hard-coded values for tokens, standardize spacing and layout, and align interaction/motion patterns.
  • Cleanup and quality assurance: Consolidate reusable components into shared libraries, remove orphaned code, run lint/type/test checks, and document changes for future maintenance.
  • Use case: Convert a bespoke checkout widget into system-compliant components that use design tokens, consistent spacing, and verified accessibility states so it matches other product areas.

Quick Start

Normalize the FEATURE by replacing custom UI elements with design system components, converting hard-coded styles to design tokens, and verifying accessibility, responsive behavior, and tests.

Frequently Asked Questions about normalize

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

FAQPage Schema
How do I normalize inconsistent frontend UI to match a design system?

To normalize frontend UI, replace custom components with design system equivalents, convert hard-coded styles to tokens, and verify accessibility, responsive behavior, and tests to eliminate visual drift.

What is the best way to remove one-off styles during a UI refactor?

The best way to remove one-off styles during a UI refactor is to audit feature components for deviations, replace bespoke patterns with design system equivalents, and consolidate reusable code into shared libraries.

When do I need to audit frontend UI for design system compliance?

You need to audit frontend UI for design system compliance during redesigns, refactors, or pre-release audits to identify and fix visual drift, accessibility regressions, and functional mismatches in interaction flows.

Can I use this to fix accessibility and responsive behavior in custom widgets?

Yes, you can normalize custom widgets by replacing bespoke UI elements with system-compliant components, swapping hard-coded values for design tokens, and verifying accessibility states and responsive breakpoints.

Does normalizing UI affect existing hard-coded values and component patterns?

Yes, normalizing UI directly impacts existing code by replacing hard-coded values with design tokens, standardizing layout spacing, aligning motion patterns, and removing orphaned code through lint and type checks.