mcpbeat

Component Design Systems

cosmicstack-labs/component-design-systems

Building and maintaining scalable component libraries, design tokens, accessibility, and cross-team collaboration patterns

448 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
365
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill component-design-systems

The instruction itself

4 sections, as written by the author

Component Design Systems

Patterns for building scalable, accessible, and maintainable component libraries.

Architecture

design-system/
├── tokens/              # Design tokens
│   ├── colors.json
│   ├── typography.json
│   └── spacing.json
├── primitives/          # Base components
│   ├── Button/
│   ├── Input/
│   └── Text/
├── patterns/            # Composed patterns
│   ├── FormField/
│   ├── DataTable/
│   └── Modal/
└── docs/               # Documentation
    └── Storybook/

Component API Design

// Compound component pattern
<Select>
  <Select.Label>Country</Select.Label>
  <Select.Trigger>
    <Select.Value placeholder="Select a country" />
  </Select.Trigger>
  <Select.Content>
    <Select.Item value="us">United States</Select.Item>
    <Select.Item value="uk">United Kingdom</Select.Item>
  </Select.Content>
</Select>

Common Mistakes

  • No design tokens: Hardcoded values everywhere. Use tokens for colors, spacing, typography.
  • Missing accessibility: Always include ARIA labels, keyboard nav, focus management.
  • Too opinionated: Components should work out-of-box but be customizable via props/composition.
  • No versioning strategy: Use semver. Document breaking changes clearly.
  • No visual regression tests: Use Chromatic/Percy to catch unintended style changes.

How to use it

Copy the folder

Take cosmicstack-labs/component-design-systems from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.