kimtth Goal: recover the implicit design system already in the code.
Use for:
- inconsistent UI grown without a defined system
- documenting tokens and patterns for reuse
- preparing a refactor toward shared components
Workflow:
- Inventory colors, spacing, type, radius, and shadow values in use.
- Cluster near-duplicates into canonical tokens.
- Identify repeated component shapes (buttons, cards, inputs).
- Note variant axes: size, intent, and state.
- Document the tokens and components with usage rules.
- Flag outliers to reconcile and propose the migration order.
Capture:
- token tables with names and values
- component catalog with variants
- spacing and type scales
- inconsistencies and one-offs to resolve
Rules:
- derive tokens from real usage, not invention
- collapse accidental near-duplicates deliberately
- keep names semantic so intent survives refactors
- record outliers instead of silently normalizing them