create-a-component-inventory

name	create-a-component-inventory
category	design
description	Inventory repeated interface patterns, variants, states, implementations, and ownership. Use when a product needs evidence for consolidation, design-system planning, accessibility repair, or migration scope.

create-a-component-inventory

Procedure

1. Define products, platforms, repositories, routes, libraries, states, and date of observation.
2. Collect components from code, design files, screenshots, rendered pages, and usage telemetry.
3. Group by user purpose before visual similarity.
4. Record name, source, owner, consumers, variants, states, behavior, accessibility, tokens, dependencies, and status.
5. Preserve near-duplicates until behavior and contracts are compared.
6. Flag orphaned, conflicting, inaccessible, unowned, deprecated, and one-off patterns.
7. Link representative live examples and implementation references.
8. Propose adopt, align, merge, replace, retire, exempt, or investigate with impact.
9. Have design and engineering owners verify a sample and disputed groups.

Guardrails

• Do not infer usage from design files alone.
• Keep private routes and security-sensitive details restricted.
• Similar appearance does not prove interchangeable behavior.

Done

• A component inventory lists evidence, consumers, states, owners, and decisions
• Code, design, and rendered samples are reconciled
• Duplicate and retirement proposals have verified impact