ui-consolidation
Installation
SKILL.md
UI Consolidation
Every change this skill produces is an internal refactor — pages render the same UI with the same behaviour. The goal is fewer components, clearer ownership, and easier future changes.
Component hierarchy
Components live at three levels. Adapt these locations to your repo’s actual package and route structure.
| Level | Location | Scope | What belongs here |
|---|---|---|---|
| 1. Design primitives | <design-system>/components/ |
Any app, any page, any context | Context-free building blocks: Button, Dialog, Card, Select, DataTable, Tooltip. No business logic. |
| 2. Feature components | <app>/components/shared/ |
Shared across multiple pages within the app | Business-aware assemblies built from Level 1 primitives. Understand domain concepts. |
| 3. Page-local components | Inside a specific route folder (e.g. <app>/routes/chat/) |
Only that one page | Components that only make sense in one context. If a second page needs the same thing, promote to Level 2. |