In short
Atomic Design gives you a vocabulary for UI pieces, from a single button up to a full page. It helps you and your designer talk about the same thing.
A methodology for organizing UI components in a hierarchy — atoms (buttons, inputs) → molecules (search bar) → organisms (header) → templates → pages.

Think of it like this
Building a house, brick by brick
Bricks and cement become a wall. Walls and a door become a room. Rooms become a floor plan, and the plan with real furniture is your home. UI grows the same way, from tiny pieces to full pages.
Watch it happen
From atoms to a page
1/5Atoms first: Input, Button and Logo. Small, with no business logic.
The big ideas
What you need to know
Atoms
The smallest pieces: a button, an input, a label, an icon.
Molecules
A few atoms working together, like a search bar made of an input and a button.
Organisms
Bigger sections made of molecules, like a header with logo, search and menu.
Templates and pages
Templates arrange organisms into a layout. Pages are templates filled with real content.
Save yourself the pain
Common mistakes
Oops
Arguing for an hour whether a card is a molecule or an organism.
Do this instead
The labels are a thinking tool. If the team agrees and moves on, either answer is fine.
Oops
Making folders for all five levels in a tiny app.
Do this instead
Use the idea, not necessarily the folders. Many teams keep just ui and sections folders.
Your mission
Break down a real screen
Quick check
In Atomic Design, where does a product card with an image, title, price and "Add to cart" button fit best?
Go deeper
- 1Categorize an existing project's components into atoms/molecules/organisms.
- 2Build one new feature deliberately following the atomic hierarchy.
- 3Notice where the strict hierarchy feels natural vs where it feels forced.
More topics at this stop
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.