# Atomic Design

Atomic design is a five-level mental model for building interfaces from small elements into components, sections, layouts, and real content instances.

- Type: framework
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/atomic-design/>)

## What it means

Brad Frost’s atomic design methodology describes atoms, molecules, organisms, templates, and pages as concurrent levels of an interface system. It encourages teams to see both reusable parts and assembled experiences rather than designing only isolated pages or only tiny components.

## Why it matters

The model gives multidisciplinary teams a vocabulary for discussing composition and testing changes at several levels. Moving between parts and whole experiences can expose whether a reusable element survives realistic content and context.

## When to use it

Use it as an organizing lens when decomposing interfaces, structuring a pattern library, or planning component composition. Adapt the labels when they create more debate than clarity; the compositional reasoning matters more than taxonomy purity.

## How it works

1. Identify foundational elements that cannot be usefully decomposed further.
2. Combine elements into small components with one coherent responsibility.
3. Assemble components into larger interface regions.
4. Place regions into content-agnostic page structures or templates.
5. Test templates with representative real content as pages.
6. Iterate nonlinearly between levels as evidence exposes weak abstractions.

## A practical example

A commerce team treats labels, inputs, and help text as elements of a field component; fields and actions form a checkout section; sections form a checkout template. Real addresses, long errors, and translated labels are then used at page level to challenge the abstractions.

## Where it breaks

The chemistry metaphor is not an objective classification system. Teams disagree about level boundaries, and modern component composition may not map neatly to five layers. Over-focusing on classification can distract from user needs, behavior, ownership, and accessibility.

## Common mistakes

- Treating the five levels as a rigid production workflow.
- Testing only atoms and molecules instead of complete pages.
- Assuming smaller components are always more reusable.
- Using atomic labels without documenting behavior and content constraints.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/atomic-design/#visualization-atomic-design>)

## Sources

1. [Atomic Design Methodology](<https://atomicdesign.bradfrost.com/chapter-2/>) — Brad Frost · Original author
2. [Atomic Design: Designing Systems](<https://atomicdesign.bradfrost.com/chapter-1/>) — Brad Frost · Original author
3. [Maintaining Design Systems](<https://atomicdesign.bradfrost.com/chapter-5/>) — Brad Frost · Original author

## Related topics

- [Component Library](<https://wiki.soroush.uk/topic/component-library/>)
- [Pattern Library](<https://wiki.soroush.uk/topic/pattern-library/>)
- [Design System](<https://wiki.soroush.uk/topic/design-system/>)
