frameworkExperience & interface

Atomic Design

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

Download Markdown (.md)

01What 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.[1][2][3]

Concurrent system levels Move between reusable parts and assembled experiences
  1. PagesTemplates with real content
  2. TemplatesContent-agnostic structures
  3. OrganismsInterface regions
  4. MoleculesSmall components
  5. AtomsFoundational elements

The levels support nonlinear iteration, not a one-way pipeline.

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. Atomic Design MethodologyBrad Frost · Original authorAtomic Design Methodology
  2. Atomic Design: Designing SystemsBrad Frost · Original authorAtomic Design: Designing Systems
  3. Maintaining Design SystemsBrad Frost · Original authorMaintaining Design Systems
View saved topics

Start typing to search titles, definitions, categories, and frameworks.