---
id: sm-normalize
name: "normalize"
url: https://skills.yangsir.net/skill/sm-normalize
author: pbakaus
domain: ai-data-management-analysis
tags: ["data-normalization", "data-cleaning", "database-design", "data-transformation", "sql"]
install_count: 54600
rating: 4.70 (1716 reviews)
github: https://github.com/pbakaus/impeccable
---

# normalize

> 此技能运用设计语言，旨在规范AI工具在数据分析过程中的处理方式，确保数据的一致性和标准化，从而提高分析结果的准确性和可靠性。

**Stats**: 54,600 installs · 4.7/5 (1716 reviews)

## Before / After 对比

### 数据标准化处理效率提升

## Readme

# normalize

Analyze and redesign the feature to perfectly match our design system standards, aesthetics, and established patterns.

## MANDATORY PREPARATION

Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.

## Plan

Before making changes, deeply understand the context:

- 

**Discover the design system**: Search for design system documentation, UI guidelines, component libraries, or style guides (grep for "design system", "ui guide", "style guide", etc.). Study it thoroughly until you understand:

Core design principles and aesthetic direction

- Target audience and personas

- Component patterns and conventions

- Design tokens (colors, typography, spacing)

**CRITICAL**: If something isn't clear, ask. Don't guess at design system principles.

- 

**Analyze the current feature**: Assess what works and what doesn't:

Where does it deviate from design system patterns?

- Which inconsistencies are cosmetic vs. functional?

- What's the root cause—missing tokens, one-off implementations, or conceptual misalignment?

- 

**Create a normalization plan**: Define specific changes that will align the feature with the design system:

Which components can be replaced with design system equivalents?

- Which styles need to use design tokens instead of hard-coded values?

- How can UX patterns match established user flows?

**IMPORTANT**: Great design is effective design. Prioritize UX consistency and usability over visual polish alone. Think through the best possible experience for your use case and personas first.

## Execute

Systematically address all inconsistencies across these dimensions:

- **Typography**: Use design system fonts, sizes, weights, and line heights. Replace hard-coded values with typographic tokens or classes.

- **Color & Theme**: Apply design system color tokens. Remove one-off color choices that break the palette.

- **Spacing & Layout**: Use spacing tokens (margins, padding, gaps). Align with grid systems and layout patterns used elsewhere.

- **Components**: Replace custom implementations with design system components. Ensure props and variants match established patterns.

- **Motion & Interaction**: Match animation timing, easing, and interaction patterns to other features.

- **Responsive Behavior**: Ensure breakpoints and responsive patterns align with design system standards.

- **Accessibility**: Verify contrast ratios, focus states, ARIA labels match design system requirements.

- **Progressive Disclosure**: Match information hierarchy and complexity management to established patterns.

**NEVER**:

- Create new one-off components when design system equivalents exist

- Hard-code values that should use design tokens

- Introduce new patterns that diverge from the design system

- Compromise accessibility for visual consistency

This is not an exhaustive list—apply judgment to identify all areas needing normalization.

## Clean Up

After normalization, ensure code quality:

- **Consolidate reusable components**: If you created new components that should be shared, move them to the design system or shared UI component path.

- **Remove orphaned code**: Delete unused implementations, styles, or files made obsolete by normalization.

- **Verify quality**: Lint, type-check, and test according to repository guidelines. Ensure normalization didn't introduce regressions.

- **Ensure DRYness**: Look for duplication introduced during refactoring and consolidate.

Remember: You are a brilliant frontend designer with impeccable taste, equally strong in UX and UI. Your attention to detail and eye for end-to-end user experience is world class. Execute with precision and thoroughness.
Weekly Installs17.8KRepository[pbakaus/impeccable](https://github.com/pbakaus/impeccable)GitHub Stars10.2KFirst Seen14 days agoSecurity Audits[Gen Agent Trust HubPass](/pbakaus/impeccable/normalize/security/agent-trust-hub)[SocketPass](/pbakaus/impeccable/normalize/security/socket)[SnykPass](/pbakaus/impeccable/normalize/security/snyk)Installed oncodex17.5Kopencode17.4Kgithub-copilot17.4Kgemini-cli17.4Kcursor17.4Kamp17.4K

---
*Source: https://skills.yangsir.net/skill/sm-normalize*
*Markdown mirror: https://skills.yangsir.net/api/skill/sm-normalize/markdown*