Atomic Design

What it does

This skill enables AI agents to generate UI components based on atomic design principles. It guides the creation of reusable and scalable interface elements by organizing them into a hierarchy: atoms, molecules, organisms, and templates. The goal is to create a component system with clear responsibilities, shared vocabulary, and isolated testability for each piece.

When to use it

• When building new user interfaces from scratch.
• To establish a consistent design language across a project.
• For teams seeking improved communication and understanding of UI components.

Key capabilities

• Atomic Design Hierarchy: Guides component creation through atoms, molecules, organisms, and templates.
• Component Naming Conventions: Encourages naming components based on their function ("what they ARE") rather than the data they display.
• Size Limits: Suggests keeping atoms under 50 lines of code and molecules under 100 lines.
• Presentational Components: Promotes building UI components that render output, receive data via props, and avoid handling data fetching or business logic.
• Design Token Usage: Emphasizes using design tokens (for colors, spacing, typography) instead of hardcoded values within components.

Example prompts

• "Generate an atom for a button component."
• "Create a molecule combining a label and input field to form a form field."
• "Design an organism representing a navigation header."
• “Show me the structure of a template for an authentication page.”

Tips & gotchas

• Start with Atoms: Always begin component creation at the atom level.
• Don't Skip Levels: Ensure all levels (atom, molecule, organism, template) are addressed sequentially.
• Separate Concerns: Keep presentational components separate from data containers to avoid mixing rendering logic and business logic.