Overview
Every product that has been built by more than one designer over more than one year has a component library problem. There are three buttons. Two modal implementations. A card component that was rebuilt four times because no one could find the original. A color palette where the same blue exists as six different hex values across different files. This is design debt — and it compounds exactly like technical debt.
The Component Library Audit & Consolidation Prompt builds a systematic audit methodology: how to inventory what exists, identify what is duplicated or inconsistent, and produce a consolidation plan that reduces complexity without breaking the product.
What you get: - Audit methodology: how to inventory components across design files and production code - Duplication analysis: how to identify components that solve the same problem differently - Inconsistency taxonomy: the 5 types of inconsistency and how to classify each - Design-to-code drift analysis: how to identify components that exist in design but not code, or vice versa - Consolidation decision framework: merge / deprecate / rebuild / keep — with decision criteria - Consolidation roadmap: the sequence for reducing component count without breaking the product - The metric that proves the audit was worth doing
Built for: design leads and design engineers who need to bring order to a component library that has grown organically — and who need a plan that can be executed without stopping product delivery.