- Home
- Skills
- Frontend & Web Apps
- atomic design
atomic design
Enforce Atomic Design hierarchy and reuse repo-specific UI primitives in React and Next.js projects.
Free
Works with the AI Agents you already use
atomic design
Example session with this skill installed
Refactor the ProfileHeader in the account feature. It currently uses raw divs and spans. Move it to the correct atomic layer and use repo primitives.
- Read your context and instructions
- Compiled the atomic design
- Generated the UI component
I have refactored ProfileHeader from a raw JSX component into a structured Organism. I replaced native HTML tags with FlexAtom and BoxAtom, and moved the layout orchestration to the presentation layer.
Refactored ProfileHeader Organism
// src/features/account/presentation/organisms/ProfileHeader/ProfileHeader.tsx
import { FlexAtom, BoxAtom, ButtonAtom, HeadingAtom } from '@/commons-ui/atoms';
import styles from './ProfileHeader.module.scss';
interface ProfileHeaderProps {
user: { name: string; avatar: string };
onEdit: () => void;
}
export const ProfileHeader = ({ user, onEdit }: ProfileHeaderProps) => {
return (
<FlexAtom direction="row" align="center" justify="between" className={styles.container}>
<FlexAtom gap="md" align="center">
<BoxAtom className={styles.avatarWrapper}>
<img src={user.avatar} alt={user.name} />
</BoxAtom>
<HeadingAtom level={2}>{user.name}</HeadingAtom>
</FlexAtom>
<ButtonAtom variant="secondary" onClick={onEdit}>
Edit Profile
</ButtonAtom>
</FlexAtom>
);
};
Next steps
- Create
ProfileHeader.module.scssin the same directory for custom spacing. - Add a
ProfileHeader.stories.tsxfile if Storybook documentation is required for this feature. - Update the
AccountTemplateto use this new organism instead of the previous inline JSX.
stories.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Maintaining a clean component hierarchy is difficult in fast-moving React projects. This skill enforces strict Atomic Design principles to prevent component bloat and ensures your UI remains modular and scalable.
What it does
- Enforces hierarchy by strictly categorizing components into atoms, molecules, organisms, templates, and pages.
- Audits layout primitives to replace raw
div,button, andimgtags with established repo atoms likeBoxAtomorButtonAtom. - Decouples logic by identifying and moving business rules out of reusable UI components.
- Orchestrates templates to ensure Next.js pages remain thin by delegating composition to the template layer.
- Refactors presentation layers by moving reusable pieces into
commons-uiwhile keeping feature-specific UI local.
How it works
- Analyze UI by reviewing existing JSX or design specs to map elements to the atomic hierarchy.
- Identify primitives by scanning for native HTML tags that should be replaced with existing repo-level atoms.
- Select layer for new components based on reusability and data dependencies.
- Scaffold components including
module.scss,__tests__/, and*.stories.tsxwhere required.
Frameworks & tools
React, Next.js, Tailwind CSS, and SASS Modules. It specifically targets architectures utilizing a commons-ui library and feature-based presentation layers.
Why this beats prompting it yourself
Generic prompts often fail to maintain the distinction between templates and organisms, leading to "fat" pages. This skill understands the specific delegation of layout orchestration and enforces the use of internal primitives over native tags.
Use cases
- Refactoring a monolithic page into reusable atoms and molecules.
- Building new features that must match existing
commons-uipatterns. - Auditing a PR to ensure no business logic has leaked into UI primitives.
- Converting Figma designs into a structured component hierarchy.
Known limitations
Does not support native JSX tags when a repo-specific atom exists. Requires a pre-existing Atomic Design folder structure to be effective.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
Requires pre-existing folder structure (atoms, molecules, etc.). Does not support projects using only native HTML tags.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 15 days ago
- Free with an Agensi account