Getting started

Atomic Design model

How this kit is organized. Based on Brad Frost's model, with the names we use at Yuno.

The 6 levels

1
Sub-atomic
Foundations

Design tokens and systemic decisions: colors, typography, iconography, spacing, radius, shadows. Not components themselves — the variables everything else consumes.

2
Atoms
Components

The indivisible atom of UI: Button, Input, Label, Badge, Checkbox, Switch. One job, highly reusable, no business logic.

3
Molecules
Patterns

Small groups of atoms working together: form field (Label + Input + hint), search box (Icon + Input), KPI card (Card + typography). Still reusable.

4
Organisms
Sections

Larger blocks made of molecules and atoms: Page header, Sidebar, Top bar, full Form, Data table, Filter bar. Already living in specific context.

5
Templates
Layouts

Reusable page structures without real content: List page, Detail page, Settings page, Wizard flow. Define where each organism lives.

6
Pages
Final prototype

The template with actual content of a specific flow. It's what the PM/designer assembles for a concrete case — discarded once it hits production.

How we apply it

Compose, don't reinvent.
When building a prototype: always start from the highest existing level. If a Template covers your case, tweak it. If an Organism serves, reuse it. Only drop down to Molecules or Atoms when composition genuinely doesn't work. This is what keeps fidelity with production.