Skip to content
TrustedSkillsbeta
Back to all skills

Atomic Design

Checked
jwilger·vlatest·frontend·CC0-1.0

Generates UI components based on atomic design principles, creating reusable and scalable interface elements.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jwilger/agent-skills --skill atomic-design -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jwilger

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jwilger/agent-skills at e2f5e19add.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e2f5e19add
Manifest
skills/atomic-design/SKILL.md
Scanned
1 file, 197 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

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.