i-normalize

Normalize feature design elements to align with design system standards.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/hi-yuki-922/accounting-assistant --skill i-normalize-hi-yuki-922
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-normalize
Source: https://github.com/hi-yuki-922/accounting-assistant/tree/main/.claude/skills/i-normalize
Command: npx skills add https://github.com/hi-yuki-922/accounting-assistant --skill i-normalize-hi-yuki-922

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that UI elements and features consistently adhere to a predefined design system, improving brand coherence and user experience.

Core Features & Use Cases

  • Design System Adherence: Analyzes and modifies features to match established design principles, tokens, and components.
  • Consistency Enforcement: Identifies and rectifies deviations in typography, color, spacing, and component usage.
  • Use Case: A new feature was developed with custom styling. This Skill will refactor it to use the company's standard design tokens and components, ensuring it looks and feels like the rest of the application.

Quick Start

Normalize the 'user-profile' feature to match the design system.

Frequently Asked Questions about i-normalize

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

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

Yes, design system normalization addresses accessibility and responsiveness by rectifying deviations in standard components. It analyzes current feature implementations and enforces design principles to ensure inclusive and adaptive user experiences.

How do I refactor custom styling to use standard design tokens?

Design system normalization handles progressive disclosure by analyzing feature implementations and aligning them with established conventions. It ensures information reveals consistently according to the predefined standards and principles of your component library.

Do I need design system documentation to enforce UI consistency?

Yes, thorough design system documentation is required to enforce UI consistency. The normalization process depends on analyzing these established standards, principles, and conventions to create a precise plan for rectifying deviations in feature components.

What is the best way to fix typography and color deviations in a component library?

The best way to fix typography and color deviations is to execute a normalization plan that compares the current feature implementation against design system documentation. This ensures strict adherence to predefined design tokens and component standards.