What problem does it solve?
This Skill prevents buttons, inputs, badges, pills, calendars, and other interface components from feeling like unrelated parts of different products. It helps create a coherent design system where shared visual and interaction patterns improve usability, recognition, and maintainability.
Core Features & Use Cases
- Shared Design DNA: Align border radii, heights, spacing, borders, shadows, colors, focus states, and interaction behaviors across component families.
- Role Clarity: Keep buttons, inputs, badges, tags, and other components visually related while making their interaction roles immediately distinguishable.
- Component Reuse: Audit existing components before creating new ones, generalize suitable one-offs, and promote repeated treatments into shared components or tokens.
- Semantic Chips: Separate tags, code tokens, keyboard hints, metrics, and other inline labels into purpose-specific components with consistent sizing and styling.
- Use Case: Apply this Skill when reviewing a component library, standardizing a form, or resolving a screen where buttons, inputs, and badges appear to come from different design systems.
Quick Start
Ask the component family consistency skill to review the interface and align its component tokens, states, interaction patterns, and semantic roles.