normalize

Normalize frontend features to align with design-system tokens and patterns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize design to match your design system and ensure consistency.

Core Features & Use Cases

  • Align interfaces with design tokens and established patterns.
  • Replace hard-coded styles with system-wide tokens.
  • Use case: when features deviate from the design system, run this to normalize.

Quick Start

Apply the design system context guidelines and run the Context Gathering Protocol to normalize the feature.

Frequently Asked Questions about normalize

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

FAQPage Schema
How do I normalize UI components to match an existing design system?

To normalize UI components, you align features with established design tokens and patterns, replacing hard-coded styles with system-wide tokens to ensure consistency across typography, color, and spacing.

What is the best way to replace hard-coded styles with design tokens?

Replacing hard-coded styles involves applying the Context Gathering Protocol to access design-system documentation and tokens, then mapping hardcoded values to the correct system-wide typography, color, and spacing patterns.

How does design system normalization handle accessibility and UI consistency?

Design system normalization handles accessibility and UI consistency by applying established tokens and patterns across all interfaces, ensuring features conform to documented accessibility standards and frontend design principles.

Do I need design-system documentation and tokens before normalizing a feature?

Yes, you need design-system documentation, tokens, and components available before normalizing a feature, because the process requires adherence to the Context Gathering Protocol to access these system definitions before making changes.

When should I run a design normalization process on my frontend project?

You should run a design normalization process when features deviate from your design system, ensuring that all hard-coded styles are replaced with standard tokens to restore UI consistency across the frontend project.