normalize

Normalize feature UI to align with design-system tokens and components.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams often implement features that drift from the established design system, leading to visual inconsistency, maintenance burden, and accessibility gaps. This skill provides a disciplined process to assess, plan, and execute alignment of a feature with tokens, components, and patterns.

Core Features & Use Cases

  • Design system alignment: Replace non-tokenized styles with design tokens and standardized components to ensure visual consistency.
  • Token-driven styling: Enforce typography, color, spacing, and motion tokens across the feature.
  • Use Case: When refactoring a UI page, run this skill to normalize typography scales, color palette, and component usage to the design system so the page matches the rest of the product.

Quick Start

Execute the normalization workflow on the target feature by applying the design system context gathered in the previous steps.

Frequently Asked Questions about normalize

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

FAQPage Schema
How do I align feature UI with my existing design system tokens?

To align feature UI with a design system, you replace non-tokenized styles with standardized typography, color, spacing, and motion tokens. This ensures visual consistency and reduces maintenance burden across your product.

What is design system normalization for frontend pages?

Design system normalization is the process of assessing and executing alignment of a feature with tokens, components, and UI patterns. It enforces consistent aesthetics, accessibility considerations, and behavior across real-world pages.

How do I refactor a UI page to use design tokens and standardized components?

You refactor a UI page by applying a disciplined normalization workflow that maps non-tokenized styles to design system tokens and standardized components. This process includes auditing steps to guarantee precise alignment and accessibility.

When do I need to normalize typography and color tokens on a feature?

You need to normalize typography and color tokens when a feature drifts from the established design system, causing visual inconsistency and accessibility gaps. This alignment ensures the feature matches the rest of the product.

What's the best way to enforce consistent component usage across a frontend feature?

The best way to enforce consistent component usage is applying a token-driven styling process that maps UI elements to standardized design system components. This includes auditing steps to guarantee precise alignment and behavior.

Does design system normalization include accessibility considerations?

Yes, design system normalization includes accessibility considerations as part of its auditing steps. Enforcing standardized tokens and component mappings guarantees precise alignment and behavioral accessibility across real-world pages.