Agent skill

Component Library

by FerroxLabs in FerroxLabs/wayland

Component library design expertise covering design system tokens, component API design, compound components, polymorphic components, accessibility by default, Storybook documentation, testing…

Apache-2.0Auto-check passedFrontend & Design

Install Component Library

skills CLI
$ npx skills add FerroxLabs/wayland --skill component-library -a claude-code

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

GitHub CLI
$ gh skill install FerroxLabs/wayland component-library --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/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/web-development/component-library .claude/skills/component-library && 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/

Facts

Skill name
component-library
GitHub stars
608
Token cost
~4.3k tokens
SKILL.md length
376 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Component library design expertise covering design system tokens, component API design, compound components, polymorphic components, accessibility by default, Storybook documentation, testing…

  • The user asks about component library
  • SKILL.md covers Purpose, Design System Token Architecture, Component API Design and Compound Components, plus 11 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Component library best practices

What it does

Component Library is an agent skill from FerroxLabs/wayland. Component library design expertise covering design system tokens, component API design, compound components, polymorphic components, accessibility by default, Storybook documentation, testing, versioning, and tree-shaking. Use when the user asks about component library, component library best practices, or needs guidance on component library implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Its SKILL.md is about 4.3k 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 and API design. It works with Storybook. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about component library
  • Component library best practices
  • Needs guidance on component library implementation
  • The user needs a different specialized skill

Example prompts

  • “/component-library”

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. 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, markdown and json).

    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 loads about 4.3k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 376 words of instructions outside code blocks.

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

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 FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 376 words, ~4,334 tokens.

Download SKILL.mdSave it as .claude/skills/component-library/SKILL.md (or your agent's skills folder).
name
component-library
description
Component library design expertise covering design system tokens, component API design, compound components, polymorphic components, accessibility by default, Storybook documentation, testing, versioning, and tree-shaking. Use when the user asks about component library, component library best practices, or needs guidance on component library implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
web-development frontend design-patterns
metadata.category
web-development
metadata.subcategory
frontend-frameworks
metadata.disclaimer
none
metadata.difficulty
intermediate

Component Library

Purpose

Design and build production-grade component libraries that serve as the foundation of a design system. This skill covers API design principles, accessibility integration, documentation, testing strategy, packaging, and long-term maintenance.

Design System Token Architecture

Token Layers
Layer 1: Global Tokens (Primitives)
  Raw design values with no semantic meaning.
  --color-blue-500: #3b82f6
  --space-4: 1rem
  --font-size-16: 1rem

Layer 2: Alias Tokens (Semantic)
  Intent-based mapping to primitives.
  --color-brand-primary: var(--color-blue-500)
  --color-text-primary: var(--color-gray-900)
  --spacing-component-gap: var(--space-4)

Layer 3: Component Tokens
  Scoped to specific components.
  --button-bg: var(--color-brand-primary)
  --button-text: var(--color-white)
  --button-radius: var(--radius-md)
  --button-padding-x: var(--space-4)
  --button-padding-y: var(--space-2)
Token File Organization
tokens/
  colors.ts       # Color primitives and semantic mappings
  spacing.ts      # Spacing scale
  typography.ts   # Font families, sizes, weights, line-heights
  borders.ts      # Border widths, radii
  shadows.ts      # Elevation system
  motion.ts       # Duration, easing curves
  breakpoints.ts  # Responsive breakpoints
  z-index.ts      # Z-index scale
  index.ts        # Combined export
Token Implementation
ts
// tokens/colors.ts
export const colors = {
  primitives: {
    blue: { 50: '#eff6ff', 100: '#dbeafe', 500: '#3b82f6', 700: '#1d4ed8', 900: '#1e3a5c' },
    gray: { 50: '#f9fafb', 100: '#f3f4f6', 500: '#6b7280', 700: '#374151', 900: '#111827' },
    red:  { 50: '#fef2f2', 500: '#ef4444', 700: '#b91c1c' },
    green: { 50: '#f0fdf4', 500: '#22c55e', 700: '#15803d' },
  },
  semantic: {
    brand: { primary: '{blue.500}', hover: '{blue.700}' },
    text: { primary: '{gray.900}', secondary: '{gray.500}', inverse: '{gray.50}' },
    bg: { primary: '#ffffff', secondary: '{gray.50}', surface: '{gray.100}' },
    border: { default: '{gray.200}', focus: '{blue.500}' },
    status: {
      success: { text: '{green.700}', bg: '{green.50}' },
      error: { text: '{red.700}', bg: '{red.50}' },
    },
  },
} as const;

Component API Design

Principles
1. SIMPLE THINGS SHOULD BE SIMPLE
   <Button>Save</Button>               -- 90% of usage
   <Button variant="danger" size="lg">  -- customization when needed

2. PROGRESSIVE DISCLOSURE
   Common props are top-level.
   Advanced props are grouped or use compound pattern.

3. CONSISTENT PROP NAMING
   variant (not type, kind, style)
   size (not sz, sizing)
   disabled (boolean, not isDisabled)
   onValueChange (not onChange, onUpdate, handleChange)

4. SENSIBLE DEFAULTS
   Every prop should have a default that covers the most common case.
   <Input type="text" />   -- type defaults to "text"
   <Button variant="primary" size="md" />  -- variant and size have defaults

5. COMPOSITION OVER CONFIGURATION
   Prefer compound components over mega-props.
   BAD:  <Select options={[]} renderOption={} renderGroup={} />
   GOOD: <Select><Select.Option /><Select.Group /></Select>
Button API Example (Comprehensive)
tsx
interface ButtonProps extends React.ButtonHTMLAttributes<HTMLButtonElement> {
  /** Visual style variant */
  variant?: 'primary' | 'secondary' | 'outline' | 'ghost' | 'danger';
  /** Size of the button */
  size?: 'sm' | 'md' | 'lg';
  /** Show loading spinner and disable interaction */
  loading?: boolean;
  /** Content before the button label */
  leftIcon?: React.ReactNode;
  /** Content after the button label */
  rightIcon?: React.ReactNode;
  /** Full width of parent container */
  fullWidth?: boolean;
  /** Render as a different element (e.g., anchor) */
  asChild?: boolean;
}

const Button = forwardRef<HTMLButtonElement, ButtonProps>(
  ({ variant = 'primary', size = 'md', loading, leftIcon, rightIcon,
     fullWidth, disabled, children, className, asChild, ...props }, ref) => {
    const isDisabled = disabled || loading;

    const classes = cn(
      'button',
      `button--${variant}`,
      `button--${size}`,
      fullWidth && 'button--full',
      isDisabled && 'button--disabled',
      className,
    );

    return (
      <button ref={ref} className={classes} disabled={isDisabled}
              aria-busy={loading || undefined} {...props}>
        {loading && <Spinner size={size} aria-hidden="true" />}
        {!loading && leftIcon && <span className="button__icon">{leftIcon}</span>}
        <span className="button__label">{children}</span>
        {rightIcon && <span className="button__icon">{rightIcon}</span>}
      </button>
    );
  }
);

Button.displayName = 'Button';

Compound Components

tsx
// Dialog compound component
const DialogContext = createContext<DialogContextValue | null>(null);

function useDialogContext() {
  const ctx = useContext(DialogContext);
  if (!ctx) throw new Error('Dialog components must be used within <Dialog>');
  return ctx;
}

function Dialog({ open, onOpenChange, children }: DialogProps) {
  return (
    <DialogContext.Provider value={{ open, onOpenChange }}>
      {children}
    </DialogContext.Provider>
  );
}

function DialogTrigger({ children, asChild }: DialogTriggerProps) {
  const { onOpenChange } = useDialogContext();
  return <button onClick={() => onOpenChange(true)}>{children}</button>;
}

function DialogContent({ children, title, description }: DialogContentProps) {
  const { open, onOpenChange } = useDialogContext();
  if (!open) return null;

  return createPortal(
    <div className="dialog-overlay" onClick={() => onOpenChange(false)}>
      <div className="dialog-content" role="dialog" aria-modal="true"
           aria-labelledby={title ? 'dialog-title' : undefined}
           onClick={(e) => e.stopPropagation()}>
        {title && <h2 id="dialog-title">{title}</h2>}
        {description && <p id="dialog-desc">{description}</p>}
        {children}
      </div>
    </div>,
    document.body
  );
}

function DialogClose({ children }: { children: React.ReactNode }) {
  const { onOpenChange } = useDialogContext();
  return <button onClick={() => onOpenChange(false)}>{children}</button>;
}

Dialog.Trigger = DialogTrigger;
Dialog.Content = DialogContent;
Dialog.Close = DialogClose;

// Usage
<Dialog open={isOpen} onOpenChange={setIsOpen}>
  <Dialog.Trigger>Open Settings</Dialog.Trigger>
  <Dialog.Content title="Settings">
    <p>Configure your preferences.</p>
    <Dialog.Close>Done</Dialog.Close>
  </Dialog.Content>
</Dialog>

Polymorphic Components

tsx
// Type-safe polymorphic `as` prop
type PolymorphicRef<C extends React.ElementType> = React.ComponentPropsWithRef<C>['ref'];

type PolymorphicProps<C extends React.ElementType, Props = {}> = Props & {
  as?: C;
} & Omit<React.ComponentPropsWithoutRef<C>, keyof Props | 'as'>;

type PolymorphicPropsWithRef<C extends React.ElementType, Props = {}> =
  PolymorphicProps<C, Props> & { ref?: PolymorphicRef<C> };

// Usage in component
type TextProps<C extends React.ElementType = 'span'> = PolymorphicPropsWithRef<C, {
  variant?: 'body' | 'heading' | 'caption' | 'code';
  size?: 'sm' | 'md' | 'lg';
  weight?: 'regular' | 'medium' | 'bold';
}>;

function Text<C extends React.ElementType = 'span'>({
  as, variant = 'body', size = 'md', weight = 'regular',
  className, children, ...props
}: TextProps<C>) {
  const Component = as || 'span';
  return (
    <Component className={cn('text', `text--${variant}`, `text--${size}`, className)} {...props}>
      {children}
    </Component>
  );
}

// Usage
<Text>Default span</Text>
<Text as="h1" variant="heading" size="lg">Page Title</Text>
<Text as="a" href="/about">Link text</Text>
<Text as="label" htmlFor="email">Email</Text>

Accessibility by Default

Built-in A11y Patterns
tsx
// All interactive components must include:
// 1. Keyboard support
// 2. ARIA attributes
// 3. Focus management
// 4. Screen reader announcements

// Example: Switch component with built-in a11y
function Switch({ checked, onCheckedChange, label, id }: SwitchProps) {
  const switchId = id || useId();

  return (
    <div className="switch-wrapper">
      <label htmlFor={switchId} className="switch-label">{label}</label>
      <button
        id={switchId}
        role="switch"
        aria-checked={checked}
        onClick={() => onCheckedChange(!checked)}
        onKeyDown={(e) => {
          if (e.key === ' ' || e.key === 'Enter') {
            e.preventDefault();
            onCheckedChange(!checked);
          }
        }}
        className={cn('switch', checked && 'switch--checked')}
      >
        <span className="switch-thumb" />
      </button>
    </div>
  );
}

// A11y testing in every component test
test('Switch is accessible', async () => {
  const { container } = render(<Switch label="Dark mode" checked={false} onCheckedChange={() => {}} />);
  expect(await axe(container)).toHaveNoViolations();
});
A11y Checklist for Every Component
[ ] Has visible label or aria-label
[ ] Keyboard operable (Tab, Enter, Space, Escape, Arrow keys as appropriate)
[ ] Focus indicator visible
[ ] Color contrast meets WCAG AA
[ ] Works with screen readers (test with NVDA/VoiceOver)
[ ] Supports prefers-reduced-motion
[ ] Error states have aria-invalid and aria-describedby
[ ] Loading states have aria-busy
[ ] Dynamic content uses aria-live
[ ] Touch target at least 24x24px

Storybook Documentation

Story Structure
tsx
// Button.stories.tsx
import type { Meta, StoryObj } from '@storybook/react';
import { Button } from './Button';

const meta: Meta<typeof Button> = {
  title: 'Components/Button',
  component: Button,
  tags: ['autodocs'],
  argTypes: {
    variant: {
      control: 'select',
      options: ['primary', 'secondary', 'outline', 'ghost', 'danger'],
      description: 'Visual style of the button',
      table: { defaultValue: { summary: 'primary' } },
    },
    size: {
      control: 'radio',
      options: ['sm', 'md', 'lg'],
    },
    loading: { control: 'boolean' },
    disabled: { control: 'boolean' },
    onClick: { action: 'clicked' },
  },
  parameters: {
    docs: {
      description: {
        component: 'Primary UI component for user interaction.',
      },
    },
  },
};
export default meta;

type Story = StoryObj<typeof Button>;

export const Primary: Story = {
  args: { children: 'Button', variant: 'primary' },
};

export const AllVariants: Story = {
  render: () => (
    <div style={{ display: 'flex', gap: '1rem' }}>
      <Button variant="primary">Primary</Button>
      <Button variant="secondary">Secondary</Button>
      <Button variant="outline">Outline</Button>
      <Button variant="ghost">Ghost</Button>
      <Button variant="danger">Danger</Button>
    </div>
  ),
};

export const Loading: Story = {
  args: { children: 'Saving...', loading: true },
};

Testing Components

tsx
// Unit test with Testing Library
import { render, screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';

describe('Button', () => {
  it('renders with correct text', () => {
    render(<Button>Click me</Button>);
    expect(screen.getByRole('button', { name: 'Click me' })).toBeInTheDocument();
  });

  it('calls onClick when clicked', async () => {
    const onClick = vi.fn();
    render(<Button onClick={onClick}>Click me</Button>);
    await userEvent.click(screen.getByRole('button'));
    expect(onClick).toHaveBeenCalledOnce();
  });

  it('does not call onClick when disabled', async () => {
    const onClick = vi.fn();
    render(<Button onClick={onClick} disabled>Click me</Button>);
    await userEvent.click(screen.getByRole('button'));
    expect(onClick).not.toHaveBeenCalled();
  });

  it('shows spinner when loading', () => {
    render(<Button loading>Save</Button>);
    expect(screen.getByRole('button')).toHaveAttribute('aria-busy', 'true');
  });

  it('passes axe accessibility checks', async () => {
    const { container } = render(<Button>Accessible</Button>);
    expect(await axe(container)).toHaveNoViolations();
  });
});

// Visual regression with Chromatic or Playwright
// Snapshot each story automatically

Versioning and Release Strategy

Semantic Versioning Rules
MAJOR (X.0.0): Breaking changes
  - Removing a prop
  - Changing default behavior
  - Renaming a component
  - Changing TypeScript types in breaking way

MINOR (0.X.0): New features (backwards compatible)
  - Adding a new component
  - Adding a new prop (with default value)
  - Adding a new variant

PATCH (0.0.X): Bug fixes
  - Fixing a visual bug
  - Fixing a11y issue
  - Fixing TypeScript type accuracy
Changelog Convention
markdown
## [2.1.0] - 2025-03-15
### Added
- `Tooltip` component with hover and focus triggers
- `fullWidth` prop to `Button` component

### Fixed
- `Select` dropdown now correctly positions in scroll containers
- `Dialog` focus trap includes dynamically added elements

### Deprecated
- `Modal` component: use `Dialog` instead (will be removed in 3.0)

Tree-Shaking and Package Build

json
// package.json
{
  "name": "@myorg/ui",
  "version": "2.1.0",
  "sideEffects": ["*.css"],
  "main": "dist/cjs/index.js",
  "module": "dist/esm/index.js",
  "types": "dist/types/index.d.ts",
  "exports": {
    ".": {
      "import": "./dist/esm/index.js",
      "require": "./dist/cjs/index.js",
      "types": "./dist/types/index.d.ts"
    },
    "./Button": {
      "import": "./dist/esm/Button.js",
      "require": "./dist/cjs/Button.js",
      "types": "./dist/types/Button.d.ts"
    },
    "./styles.css": "./dist/styles.css"
  },
  "files": ["dist"]
}

Component Library Checklist

  • Token system defined (primitives -> semantic -> component tokens)
  • Component API follows consistent naming conventions
  • Every component has TypeScript types with JSDoc descriptions
  • Compound components used for complex composite UIs
  • Polymorphic as prop available on layout/text components
  • Every interactive component is keyboard accessible
  • Every component has Storybook stories with controls
  • Every component has unit tests + a11y tests
  • Visual regression tests configured (Chromatic or Playwright)
  • Package exports enable tree-shaking
  • sideEffects field correctly configured
  • Semantic versioning enforced via changesets
  • CHANGELOG maintained with each release
  • forwardRef used on all components that wrap native elements

When to Use

Use this skill when:

  • Designing or implementing component library solutions
  • Reviewing or improving existing component library approaches
  • Making architectural or implementation decisions about component library
  • Learning component library patterns and best practices
  • Troubleshooting component library-related issues

Do NOT use this skill when:

  • The question is about a fundamentally different technology domain
  • A more specific sibling skill covers the exact topic needed
  • The user needs a complete hands-on tutorial rather than expert guidance
Show full SKILL.md (123 more words)Show less

Output Format

markdown
# Component Library Analysis

## Context Assessment
[Situation summary and constraints]

## Recommended Approach
[Primary recommendation with rationale]

## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]

## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]

## Next Steps
- [Immediate action item]
- [Follow-up action item]

Example

Input: "Help me implement component library for a medium-scale production application"

Output: A structured analysis covering current state assessment, recommended component library approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.

Edge Cases

  • Legacy system integration: When component library must coexist with legacy approaches, provide a gradual migration path rather than a complete rewrite
  • Scale mismatch: When the solution complexity exceeds the project scale, recommend a simpler approach and note when to revisit
  • Team skill gaps: When the team lacks experience with the recommended approach, include learning resources and simpler alternatives
  • Conflicting requirements: When constraints conflict (e.g., performance vs. maintainability), explicitly state the trade-off and recommend based on stated priorities

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/web-development/component-library of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Component Library 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Component Library this skillFerroxLabs/wayland608—~4.3kAutomated safety check: PassApache-2.0
Component Library Patternsvibeeval/vibecosystem531—~764Automated safety check: PassMIT
Run Umbraco UIumbraco/Umbraco.UI152—~1.2kAutomated safety check: PassMIT
Wonder BlocksKhan/wonder-blocks163—~3.2kAutomated safety check: PassMIT
DaleuiDaleStudy/daleui119—~675Automated safety check: PassMIT
Storylite Create Storyitsjavi/storylite143—~1.4kAutomated safety check: PassMIT

Similar skills

  • Component Library Patterns

    vibeeval/vibecosystem

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

    531 GitHub stars~764 tokensUpdated 1 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 today
    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 yesterday
    Frontend & DesignAuto-check passed
  • Storylite Create Story

    itsjavi/storylite

    Create StoryLite component stories in consumer projects that use StoryLite public packages, explaining StoryLite's CSF-like story format with examples from single-story files to advanced args…

    143 GitHub stars~1.4k tokensUpdated 12 days ago
    Frontend & DesignAuto-check passed
  • Storybook

    Khan/wonder-blocks

    Storybook best practices for Wonder Blocks component stories.

    163 GitHub stars~4.2k tokensUpdated today
    Frontend & DesignAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Component Library

What does Component Library do?

Component library design expertise covering design system tokens, component API design, compound components, polymorphic components, accessibility by default, Storybook documentation, testing…. Component Library is an agent skill from FerroxLabs/wayland. Component library design expertise covering design system tokens, component API design, compound components, polymorphic components, accessibility by default, Storybook documentation, testing, versioning, and tree-shaking.

When should I use Component Library?

Component Library fits situations like: the user asks about component library; component library best practices; needs guidance on component library implementation; the user needs a different specialized skill.

How do I install Component Library in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill component-library -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/web-development/component-library in FerroxLabs/wayland) into .claude/skills/component-library in your project. Claude Code loads it when a task matches its description.

How do I install Component Library in Codex?

Run `npx skills add FerroxLabs/wayland --skill component-library -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/web-development/component-library in FerroxLabs/wayland) into .agents/skills/component-library in your project. Codex loads it when a task matches its description.

Can I use Component Library 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 FerroxLabs/wayland --skill component-library -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, .gemini/skills/component-library, .github/skills/component-library and .opencode/skills/component-library in your project.

What does Component Library need to run?

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

Does Component Library 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 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 use?

Component Library is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Component Library use?

About 4.3k tokens (SKILL.md is roughly 17k 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?

Skills that share tags, products or a category with Component Library: Component Library Patterns (vibeeval/vibecosystem, 531 stars), Run Umbraco UI (umbraco/Umbraco.UI, 152 stars), Wonder Blocks (Khan/wonder-blocks, 163 stars) and Daleui (DaleStudy/daleui, 119 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Component Library?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

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