Agent skill

Component Library Patterns

Design system token management, component API design, Storybook, and visual regression testing patterns

Install Component Library Patterns

skills CLI

$ npx skills add vibeeval/vibecosystem --skill component-library-patterns -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install vibeeval/vibecosystem component-library-patterns --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/component-library-patterns .claude/skills/component-library-patterns && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "component-library-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/component-library-patterns into .claude/skills/component-library-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-library-patterns", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/vibeeval/vibecosystem/tree/main/skills/component-library-patterns

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add vibeeval/vibecosystem --skill component-library-patterns -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install vibeeval/vibecosystem component-library-patterns --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/component-library-patterns .agents/skills/component-library-patterns && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "component-library-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/component-library-patterns into .agents/skills/component-library-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-library-patterns", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vibeeval/vibecosystem --skill component-library-patterns -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install vibeeval/vibecosystem component-library-patterns --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/component-library-patterns .cursor/skills/component-library-patterns && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "component-library-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/component-library-patterns into .cursor/skills/component-library-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-library-patterns", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/vibeeval/vibecosystem.git --path skills/component-library-patterns

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add vibeeval/vibecosystem --skill component-library-patterns -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install vibeeval/vibecosystem component-library-patterns --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/component-library-patterns .gemini/skills/component-library-patterns && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "component-library-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/component-library-patterns into .gemini/skills/component-library-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-library-patterns", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install vibeeval/vibecosystem component-library-patterns

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add vibeeval/vibecosystem --skill component-library-patterns -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/component-library-patterns .github/skills/component-library-patterns && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "component-library-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/component-library-patterns into .github/skills/component-library-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-library-patterns", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vibeeval/vibecosystem --skill component-library-patterns -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install vibeeval/vibecosystem component-library-patterns --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/component-library-patterns .opencode/skills/component-library-patterns && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "component-library-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/component-library-patterns into .opencode/skills/component-library-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-library-patterns", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: component-library-patterns
GitHub stars: 531
Token cost: ~764 tokens
SKILL.md length: 80 words
Files: 1
Skills in repo: 144
Repo updated: Aug 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Design system token management, component API design, Storybook, and visual regression testing patterns

Tasks that involve Design systems
SKILL.md covers Design Tokens, Component API Design, Storybook Patterns and Visual Regression Testing, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Tasks that involve Visual regression testing

What it does

Component Library Patterns is an agent skill from vibeeval/vibecosystem. Design system token management, component API design, Storybook, and visual regression testing patterns

Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Design systems, Visual regression testing and API design. It works with Storybook. The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.

When your agent uses it

Tasks that involve Design systems
Tasks that involve Visual regression testing
Tasks that involve API design

Example prompts

“/component-library-patterns”

What it can do on your machine

Read from SKILL.md and the folder at commit 3b763b1. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and css).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Component Library Patterns loads about 764 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 80 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~33
When it runs · the whole SKILL.md, loaded when a task matches: ~764

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vibeeval/vibecosystem at commit 3b763b1, republished under its MIT licence (© vibeeval). 80 words, ~764 tokens.

Download SKILL.mdSave it as .claude/skills/component-library-patterns/SKILL.md (or your agent's skills folder).

name: component-library-patterns
description: Design system token management, component API design, Storybook, and visual regression testing patterns

Component Library Patterns

Design Tokens

typescript

// tokens.ts - Single source of truth
export const tokens = {
  color: {
    primary: { 50: '#eff6ff', 500: '#3b82f6', 900: '#1e3a5f' },
    semantic: { success: '#22c55e', error: '#ef4444', warning: '#f59e0b' }
  },
  spacing: { xs: '4px', sm: '8px', md: '16px', lg: '24px', xl: '32px' },
  font: {
    size: { sm: '0.875rem', base: '1rem', lg: '1.125rem', xl: '1.25rem' },
    weight: { normal: 400, medium: 500, semibold: 600, bold: 700 }
  },
  radius: { sm: '4px', md: '8px', lg: '12px', full: '9999px' },
  shadow: {
    sm: '0 1px 2px rgba(0,0,0,0.05)',
    md: '0 4px 6px rgba(0,0,0,0.1)'
  }
} as const

Component API Design

typescript

// Composition pattern > prop explosion
// YANLIS:
<Button icon="check" iconPosition="left" loading loadingText="..." />

// DOGRU:
<Button>
  <Button.Icon><CheckIcon /></Button.Icon>
  <Button.Text>Save</Button.Text>
  <Button.Spinner />
</Button>

// Polymorphic component
interface ButtonProps<T extends ElementType = 'button'> {
  as?: T
  variant: 'primary' | 'secondary' | 'ghost'
  size: 'sm' | 'md' | 'lg'
}

Storybook Patterns

typescript

// Component.stories.tsx
const meta: Meta<typeof Button> = {
  component: Button,
  argTypes: {
    variant: { control: 'select', options: ['primary', 'secondary'] },
    size: { control: 'radio', options: ['sm', 'md', 'lg'] }
  }
}

export const Playground: Story = { args: { variant: 'primary', children: 'Click' } }
export const AllVariants: Story = {
  render: () => (
    <div style={{ display: 'flex', gap: 8 }}>
      {(['primary', 'secondary', 'ghost'] as const).map(v => (
        <Button key={v} variant={v}>{v}</Button>
      ))}
    </div>
  )
}

Visual Regression Testing

typescript

// Chromatic veya Percy ile
test('Button variants match snapshot', async ({ page }) => {
  await page.goto('/iframe.html?id=button--all-variants')
  await expect(page).toHaveScreenshot('button-variants.png', {
    maxDiffPixelRatio: 0.01
  })
})

Theming

css

/* CSS Custom Properties */
:root {
  --color-primary: #3b82f6;
  --color-bg: #ffffff;
  --color-text: #1f2937;
}

[data-theme="dark"] {
  --color-primary: #60a5fa;
  --color-bg: #111827;
  --color-text: #f9fafb;
}

Checklist

Design tokens single source of truth
Component API composition-based (slot pattern)
Her component'te Storybook story var
Visual regression test aktif
Accessibility: keyboard nav + ARIA + contrast
Theming: CSS variables ile dark/light
Semantic versioning + CHANGELOG
Prop documentation (JSDoc veya MDX)
Bundle size per-component tracked

Anti-Patterns

Prop explosion (10+ prop → composition kullan)
Token'sız hardcoded değerler
Component'te global CSS
Story'siz component
Theme switch'te flash (FOUC)
Circular dependency between components

Files

Just SKILL.md in skills/component-library-patterns of vibeeval/vibecosystem.

Open the folder on GitHubat commit 3b763b1

Compare with similar skills

Component Library Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Component Library Patterns compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Component Library Patterns this skillvibeeval/vibecosystem	531	—	~764	Automated safety check: Pass	MIT	2 mo ago
Component LibraryFerroxLabs/wayland	608	—	~4.3k	Automated safety check: Pass	Apache-2.0	yesterday
Ark UIBrandon030722/ark-ui-skill	265	—	~3.7k	Automated safety check: Pass	None	2 mo ago
Run Umbraco UIumbraco/Umbraco.UI	152	—	~1.2k	Automated safety check: Pass	MIT	yesterday
Wonder BlocksKhan/wonder-blocks	163	—	~3.2k	Automated safety check: Pass	MIT	yesterday
Vrtmarigold-ui/marigold	146	—	~787	Automated safety check: Pass	MIT	yesterday

Similar skills

Component Library
FerroxLabs/wayland
Component library design expertise covering design system tokens, component API design, compound components, polymorphic components, accessibility by default, Storybook documentation, testing…
608 GitHub stars~4.3k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Ark UI
Brandon030722/ark-ui-skill
Design, implement, audit, or refactor web and game-adjacent interfaces using an evidence-based Hypergryph visual language with two independent choices: product family and application depth (1…
265 GitHub stars~3.7k tokensUpdated 2 mo ago
Frontend & DesignAuto-check passed
Run Umbraco UI
umbraco/Umbraco.UI
Build, run, and drive the Umbraco.UI (UUI) web-component library via its Storybook.
152 GitHub stars~1.2k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Wonder Blocks
Khan/wonder-blocks
Implements user interfaces using the Wonder Blocks (WB) design system — Khan Academy's React component library.
163 GitHub stars~3.2k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Vrt
marigold-ui/marigold
DST — Trigger the Visual-Regression-Tests (Chromatic) GitHub Actions workflow on the current or a given branch.
146 GitHub stars~787 tokensUpdated yesterday
Frontend & DesignAuto-check passed
Daleui
DaleStudy/daleui
Use the daleui React design system with semantic Panda CSS tokens and accessible components.
119 GitHub stars~675 tokensUpdated 2 days ago
Frontend & DesignAuto-check passed

Questions about Component Library Patterns

What does Component Library Patterns do?

Design system token management, component API design, Storybook, and visual regression testing patterns. Component Library Patterns is an agent skill from vibeeval/vibecosystem.

When should I use Component Library Patterns?

Component Library Patterns fits situations like: tasks that involve Design systems; tasks that involve Visual regression testing; tasks that involve API design.

How do I install Component Library Patterns in Claude Code?

Run `npx skills add vibeeval/vibecosystem --skill component-library-patterns -a claude-code`. Or copy the skill folder (skills/component-library-patterns in vibeeval/vibecosystem) into .claude/skills/component-library-patterns in your project. Claude Code loads it when a task matches its description.

How do I install Component Library Patterns in Codex?

Run `npx skills add vibeeval/vibecosystem --skill component-library-patterns -a codex`. Or copy the skill folder (skills/component-library-patterns in vibeeval/vibecosystem) into .agents/skills/component-library-patterns in your project. Codex loads it when a task matches its description.

Can I use Component Library Patterns in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vibeeval/vibecosystem --skill component-library-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/component-library-patterns, .gemini/skills/component-library-patterns, .github/skills/component-library-patterns and .opencode/skills/component-library-patterns in your project.

What does Component Library Patterns need to run?

SKILL.md names no scripts, command-line tools or credentials: Component Library Patterns is instructions for the agent only.

Does Component Library Patterns access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Component Library Patterns safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Component Library Patterns use?

Component Library Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Component Library Patterns use?

About 764 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Component Library Patterns?

Skills that share tags, products or a category with Component Library Patterns: Component Library (FerroxLabs/wayland, 608 stars), Ark UI (Brandon030722/ark-ui-skill, 265 stars), Run Umbraco UI (umbraco/Umbraco.UI, 152 stars) and Wonder Blocks (Khan/wonder-blocks, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Component Library Patterns?

vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 144 skills in this directory. The repository was last updated on August 8, 2026.

Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Component Library Patterns

Install Component Library Patterns

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Component Library Patterns

Design Tokens

Component API Design

Storybook Patterns

Visual Regression Testing

Theming

Checklist

Anti-Patterns

Files

Compare with similar skills

Similar skills

Component Library

Ark UI

Run Umbraco UI

Wonder Blocks

Vrt

Daleui

More from vibeeval/vibecosystem

Agent Benchmark

Differential Review

Factcheck Guard

Fp Check

N8n Workflows

Notepad System

Questions about Component Library Patterns

Install Component Library Patterns

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Component Library Patterns

Design Tokens

Component API Design

Storybook Patterns

Visual Regression Testing

Theming

Checklist

Anti-Patterns

Files

Compare with similar skills

Similar skills

More from vibeeval/vibecosystem

Related

Questions about Component Library Patterns