jado-design-systems
Guides reuse of design system tokens and components.
- Status
- Observed
- Last reviewed
- 2026-10-10
ID: jado-design-systems.
What it does
Maps local tokens and components; applies stack-independent layout rules. Uses shadcn and Tailwind only in projects that adopt them, and better-layout when layout needs to be designed or corrected.
When to use it
Use it when a solution affects shared components, requires a new variant or must be translated from canvas to existing tokens. If composing components without changing their contract is sufficient, the UI developer can act directly.
How to use it
Ask for it by name, or invoke it with /jado-design-systems in Claude Code or $jado-design-systems in Codex. Provide the approved result, components, tokens and editable files. Specify views consuming the component. Request a reuse map, reasons for exceptions and checks on affected surfaces.
What it delivers
- Mapping from design to tokens/components
- Any authorized variants or tokens
- Exceptions and evidence from affected views
Example
Map the approved canvas to design system components and add only the necessary density variant, in the assigned files.