Consolidate duplicate components across design libraries

Scan a messy inventory of UI components to find duplicates, confusing synonyms, and overlapping variants. Use this during design system cleanups and mergers.

You getRedundant Component Clusters, inconsistent Variant Patterns and consolidation Roadmap

Prompt

Prompt
Act as a design systems lead. Audit the provided component inventory to spot duplicates, conflicting synonyms, overlapping responsibilities, and non-standard terminology.

- Identify components serving identical user needs under different labels.
- Flag inconsistent modifier patterns across components.
- Group duplicates into proposed canonical components.
- Provide an action plan prioritizing low-risk merges versus high-risk refactors.

Output format:
- Redundant Component Clusters (table with: Clustered Components, Overlap Description, Proposed Canonical Name)
- Inconsistent Variant Patterns (bullet list highlighting conflicting property logic)
- Consolidation Roadmap (Phase 1 Quick Wins, Phase 2 Breaking Merges)
- Governance Rule (2 concise rules to prevent future duplication)

My component inventory is below:

Example output

Example for: an enterprise component list containing Modal, DialogWindow, Popup, Banner, NotificationStrip, AlertBox, and DropdownSelect

Redundant Component Clusters
Clustered ComponentsOverlap DescriptionProposed Canonical Name
Modal, DialogWindowBoth open a blocking overlay with a backdrop for confirmation or form entryDialog
Banner, NotificationStrip, AlertBoxIdentical full-width container used to display system status messagesAlert
DropdownSelect, CustomPicker, OptionListShared purpose of selecting one or multiple values from a trigger menuSelect
FloatingMessage, ToastItem, SnackBarTransient corner notifications with auto-dismiss timersToast
Inconsistent Variant Patterns
  • Size attributes switch between t-shirt sizing (sm, md, lg in Buttons) and height values (32px, 40px in Selects).
  • Status indications alternate between semantic names (danger, warning) and visual terms (red, amber, caution).
  • Dismissible behavior is controlled by closeable in Alerts, hasDismiss in Banners, and onClose presence in Modals.
Consolidation Roadmap
  • Phase 1: Quick Wins (Non-breaking)

    • Alias DialogWindow to Dialog and mark the alias deprecated.
    • Standardize all size props to use sm, md, lg tokens while supporting legacy props with console warnings.
    • Consolidate color variants across Alerts to standard intent tokens: info, success, warning, danger.
  • Phase 2: Breaking Merges (Requires coordinated release)

    • Merge CustomPicker and DropdownSelect into a compound Select supporting custom item rendering.
    • Retire Popup in favor of primitive Popover for unanchored floating layers.
Governance Rules
  • Every new component proposal must identify its WAI-ARIA role before library entry to avoid cosmetic duplicates.
  • Property modifiers must use global token sets for sizing and status; custom local strings are rejected during review.
Written by AI from this prompt. Your results will vary.

Paste your exported component list, Figma library names, or UI catalog into ChatGPT, Claude, or Gemini. Ask the model to generate a team-wide migration survey to measure how many teams use each duplicate.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Design