atomic-design

Organize UI components into atoms, molecules, organisms, and templates.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/jwilger/claude-code-plugins --skill atomic-design-jwilger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atomic-design
Source: https://github.com/jwilger/claude-code-plugins/tree/main/sdlc/skills/atomic-design
Command: npx skills add https://github.com/jwilger/claude-code-plugins --skill atomic-design-jwilger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brad Frost's Atomic Design provides a robust framework for building scalable UI systems by organizing components into a disciplined hierarchy (atoms, molecules, organisms, templates). This approach reduces duplication, improves consistency, and makes design system governance easier across teams.

Core Features & Use Cases

  • Hierarchical component design: atoms → molecules → organisms → templates to enable predictable composition.
  • Design tokens and governance: centralize colors, typography, spacing to ensure cohesive theming.
  • Reusable patterns across projects: accelerate UI development with repeatable building blocks.

Quick Start

  • Define Atoms (e.g., Button, Input, Text) as the smallest reusable elements.
  • Build Molecules by combining atoms (e.g., FormField, Card).
  • Assemble Organisms into features (e.g., Navbar, LoginForm) and Templates for page layouts.
  • Document the design system with tokens and clear ownership to guide teams.

Frequently Asked Questions about atomic-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure UI components to reduce design fragmentation across projects?

Atomic design solves UI fragmentation by organizing components into a predictable hierarchy from atoms to templates, which reduces duplication and makes design system governance easier across teams.

What is the best way to build scalable UI from atoms to templates?

Building scalable UI starts by defining atoms like Button and Input, combining them into molecules like FormField, assembling organisms like Navbar, and finishing with templates to establish predictable composition and cohesive theming.

How do I centralize design tokens for colors, typography, and spacing?

Atomic design establishes design token governance by centralizing colors, typography, and spacing, ensuring cohesive theming and consistent component styling across all reusable building blocks and project pages.

Can I use atomic design across multiple frameworks without dependencies?

Yes, atomic design applies across projects and frameworks with zero dependencies, requiring only well-defined design tokens and clear component responsibilities to implement the hierarchical building blocks.

When should I not use atomic design for component-based UI development?

Atomic design may be unnecessary for small projects lacking reusable patterns or when a team cannot maintain well-defined design tokens and clear component ownership across the hierarchy.