atomic-components

Organize React UI components into atoms, molecules, organisms, and templates under src/components.

2|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/aboudou-cto-bloko/pixelmart --skill atomic-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atomic-components
Source: https://github.com/aboudou-cto-bloko/pixelmart/tree/main/.claude/skills/atomic-components
Command: npx skills add https://github.com/aboudou-cto-bloko/pixelmart --skill atomic-components

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pixel-Mart frontend teams often struggle to maintain a consistent UI across components as the product grows. This skill enforces an Atomic Design approach to shape a scalable, reusable UI system by organizing components into atoms, molecules, organisms, and templates and by guiding integration with the existing shadcn/ui foundations.

Core Features & Use Cases

  • Establishes a clear component taxonomy (atoms, molecules, organisms, templates) to keep UI consistent.
  • Provides concrete classification rules and examples to aid new contributors.
  • Guides frontend work in src/components/ with a scalable folder structure and naming conventions that support future growth in Pixel-Mart.

Quick Start

Start by organizing your UI under src/components/ into atoms, molecules, organisms, and templates.

Frequently Asked Questions about atomic-components

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

FAQPage Schema
How do I organize React UI components using atomic design?

Organizing React UI components with atomic design involves grouping elements into a fixed taxonomy of atoms, molecules, organisms, and templates. This Skill guides creating a consistent component hierarchy within src/components to maintain UI consistency as your project grows.

What is the best way to structure a scalable React component hierarchy?

Structuring a scalable React component hierarchy requires enforcing a fixed directory structure under src/components. This Skill defines concrete classification rules for atoms, molecules, organisms, and templates to support future growth and aid new contributors.

Can I use atomic design principles with existing shadcn/ui foundations?

Yes, you can apply atomic design with existing shadcn/ui foundations. This Skill provides guidelines for classifying and organizing components into atoms, molecules, organisms, and templates without modifying the base UI library itself.

How do I classify React components into atoms, molecules, and organisms?

Classifying React components involves applying concrete rules based on complexity: atoms are basic elements, molecules combine atoms, and organisms group molecules. This Skill provides specific classification examples to help standardize your frontend workflow.

Does organizing React components by atomic design modify the base UI library?

No, organizing React components by atomic design does not modify the base UI library. This Skill enforces directory structure, file naming, and classification guidelines within your project's src/components folder while leaving underlying UI foundations untouched.