component-library
Skill1 starsChanged 7 months agoMITView on GitHub
Scaffold component library structure with Storybook and documentation
- Installs packages
5 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- Bbeierle12/Skill-MCP-Claudetheir own version, first seen Nov 1, 2026
- SyedSibtainRazvi/skillstheir own version, first seen Oct 20, 2026
- genfeedai/genfeed.aitheir own version, first seen Sep 12, 2026
- Abdox-menara/guard-skillstheir own version, first seen Aug 24, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Bbeierle12/Skill-MCP-Claude★ 9same name
- genfeedai/genfeed.ai★ 4same name
- nisarth/claude-skills-store★ 1same name
- SyedSibtainRazvi/skills★ 1same name
- Abdox-menara/guard-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository206 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-healthSkill
- skill-validatorSkill
- accessibilitySkill
- agent-debugSkill
- agent-evaluateSkill
- ai-governanceSkill
- ai-system-reviewSkill
- api-docs-generateSkill
- api-examplesSkill
- api-mockSkill
- api-test-generateSkill
- api-validateSkill
- architecture-diagramSkill
- ask-mattSkill
- assumption-mapSkill
- boilerplateSkill
- brainstormSkill
- branch-finishSkill
- briefingSkill
- browser-testing-with-devtoolsSkill
- bundle-analyzeSkill
- cache-strategySkill
- canarySkill
- carefulSkill
- cavemanSkill
- changelog-autoSkill
- chaos-testSkill
- ci-setupSkill
- ci-sweepSkill
- cleanprojectSkill
- click-path-auditSkill
- codebase-designSkill
- code-review-checklistSkill
- code-tourSkill
- commitSkill
- completion-verifySkill
- complexity-reduceSkill
- config-cleanupSkill
- config-generateSkill
- conflict-resolveSkill
- container-optimizeSkill
- context-budgetSkill
- context-engineeringSkill
- context-restoreSkill
- context-saveSkill
- continuous-learningSkill
- contributingSkill
- cost-trackSkill
- councilSkill
- create-todosSkill
- cross-modal-reviewSkill
- database-connectSkill
- db-diagramSkill
- ddd-modelSkill
- debug-root-causeSkill
- debug-sessionSkill
- debug-systematicSkill
- decision-logSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 58
Check for existing Storybook installation
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Component Library Scaffolding
I'll help you set up a complete component library with Storybook, testing, documentation, and build configuration.
Arguments: $ARGUMENTS - library type or framework (e.g., "react", "vue", "web-components", "storybook")
Strategic Planning Process
<think>
Component library setup requires careful consideration:- Framework Selection
- React, Vue, Angular, Svelte, Web Components?
- TypeScript or JavaScript?
- What's the target environment? (browser, Node.js, both)
- Design system or utility components?
- Build & Distribution
- How will components be bundled? (Rollup, Vite, esbuild)
- What formats? (ESM, CJS, UMD)
- Tree-shaking support needed?
- CSS bundling strategy
- Type definitions generation
- Documentation & Development
- Storybook for component showcase
- Documentation site (Docusaurus, VitePress, etc.)
- Live playground/examples
- Design tokens documentation
- Accessibility guidelines
- Quality Assurance
- Unit testing (Jest, Vitest)
- Visual regression testing (Chromatic)
- Accessibility testing (axe, jest-axe)
- Build validation
- Bundle size tracking
- Publishing Strategy
- npm package setup
- Versioning strategy (semantic versioning)
- Changelog generation
- CI/CD for releases
</think>
Phase 1: Project Detection & Setup
MANDATORY FIRST STEPS:
- Detect existing project or create new structure
- Identify framework and build tool preferences
- Determine component library scope
- Check for existing Storybook installation
Let me analyze your project:
# Detect framework and setup
echo "=== Component Library Setup Analysis ==="
# Check for existing framework
FRAMEWORK=""
if grep -q "\"react\"" package.json 2>/dev/null; then
FRAMEWORK="React"
echo "Detected: React"
elif grep -q "\"vue\"" package.json 2>/dev/null; then
FRAMEWORK="Vue"
echo "Detected: Vue"
elif grep -q "@angular/core" package.json 2>/dev/null; then
FRAMEWORK="Angular"
echo "Detected: Angular"
elif grep -q "\"svelte\"" package.json 2>/dev/null; then
FRAMEWORK="Svelte"
echo "Detected: Svelte"
else
echo "No framework detected - will set up for your choice"
fi
# Check for TypeScript
if [ -f "tsconfig.json" ]; then
echo "TypeScript: ✓"
else
echo "TypeScript: ✗"
fi
# Check for Storybook
if [ -d ".storybook" ]; then
echo "Storybook: Already installed"
ls -la .storybook/
else
echo "Storybook: Not installed (will configure)"
fi
# Check for build tools
if [ -f "vite.config.js" ] || [ -f "vite.config.ts" ]; then
echo "Build tool: Vite"
elif [ -f "rollup.config.js" ]; then
echo "Build tool: Rollup"
elif [ -f "webpack.config.js" ]; then
echo "Build tool: Webpack"
else
echo "Build tool: None detected (will configure)"
fi
# Check for existing components
if [ -d "src/components" ]; then
echo ""
echo "Existing components:"
find src/components -type f -name "*.tsx" -o -name "*.jsx" -o -name "*.vue" 2>/dev/null | head -10
fiPhase 2: Component Library Structure
I'll create a comprehensive component library structure:
Directory Structure:
component-library/
├── src/
│ ├── components/ # Component source files
│ │ ├── Button/
│ │ │ ├── Button.tsx
│ │ │ ├── Button.test.tsx
│ │ │ ├── Button.stories.tsx
│ │ │ ├── Button.module.css
│ │ │ └── index.ts
│ │ ├── Input/
│ │ │ ├── Input.tsx
│ │ │ ├── Input.test.tsx
│ │ │ ├── Input.stories.tsx
│ │ │ └── index.ts
│ │ └── index.ts # Main exports
│ ├── hooks/ # Shared React hooks
│ ├── utils/ # Utility functions
│ ├── types/ # TypeScript types
│ └── index.ts # Library entry point
├── .storybook/ # Storybook configuration
│ ├── main.ts
│ ├── preview.ts
│ └── theme.ts
├── docs/ # Documentation
│ ├── getting-started.md
│ ├── components/
│ └── design-tokens.md
├── dist/ # Build output
│ ├── esm/ # ES Modules
│ ├── cjs/ # CommonJS
│ └── types/ # Type definitions
├── package.json
├── tsconfig.json
├── tsconfig.build.json
├── vite.config.ts # Build configuration
├── vitest.config.ts # Test configuration
├── .npmignore
└── README.mdPhase 3: Storybook Setup
I'll configure Storybook for component development:
Install Storybook:
# Initialize Storybook (auto-detects framework)
npx storybook@latest init
# Or manual installation for specific framework
npm install --save-dev @storybook/react @storybook/react-vite
npm install --save-dev @storybook/addon-essentials @storybook/addon-a11y
npm install --save-dev @storybook/addon-interactions @storybook/testStorybook Configuration (.storybook/main.ts):
import type { StorybookConfig } from '@storybook/react-vite';
const config: StorybookConfig = {
stories: ['../src/**/*.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
addons: [
'@storybook/addon-essentials',
'@storybook/addon-a11y',
'@storybook/addon-interactions',
'@storybook/addon-links',
],
framework: {
name: '@storybook/react-vite',
options: {},
},
docs: {
autodocs: 'tag',
},
staticDirs: ['../public'],
};
export default config;Storybook Preview (.storybook/preview.ts):
import type { Preview } from '@storybook/react';
import '../src/styles/global.css';
const preview: Preview = {
parameters: {
actions: { argTypesRegex: '^on[A-Z].*' },
controls: {
matchers: {
color: /(background|color)$/i,
date: /Date$/,
},
},
backgrounds: {
default: 'light',
values: [
{ name: 'light', value: '#ffffff' },
{ name: 'dark', value: '#1a1a1a' },
],
},
},
};
export default preview;Phase 4: Component Templates
I'll create example component templates:
Button Component (src/components/Button/Button.tsx):
import React from 'react';
import styles from './Button.module.css';
export interface ButtonProps
extends React.ButtonHTMLAttributes<HTMLButtonElement> {
/**
* Button variant
*/
variant?: 'primary' | 'secondary' | 'outline';
/**
* Button size
*/
size?: 'small' | 'medium' | 'large';
/**
* Loading state
*/
loading?: boolean;
/**
* Full width button
*/
fullWidth?: boolean;
}
/**
* Primary UI component for user interaction
*/
export const Button = React.forwardRef<HTMLButtonElement, ButtonProps>(
(
{
variant = 'primary',
size = 'medium',
loading = false,
fullWidth = false,
children,
disabled,
className,
...props
},
ref
) => {
const classes = [
styles.button,
styles[variant],
styles[size],
fullWidth && styles.fullWidth,
className,
]
.filter(Boolean)
.join(' ');
return (
<button
ref={ref}
className={classes}
disabled={disabled || loading}
{...props}
>
{loading ? <span className={styles.spinner} /> : children}
</button>
);
}
);
Button.displayName = 'Button';Button Stories (src/components/Button/Button.stories.tsx):
import type { Meta, StoryObj } from '@storybook/react';
import { Button } from './Button';
const meta = {
title: 'Components/Button',
component: Button,
parameters: {
layout: 'centered',
},
tags: ['autodocs'],
argTypes: {
variant: {
control: 'select',
options: ['primary', 'secondary', 'outline'],
},
size: {
control: 'select',
options: ['small', 'medium', 'large'],
},
},
} satisfies Meta<typeof Button>;
export default meta;
type Story = StoryObj<typeof meta>;
export const Primary: Story = {
args: {
variant: 'primary',
children: 'Button',
},
};
export const Secondary: Story = {
args: {
variant: 'secondary',
children: 'Button',
},
};
export const Large: Story = {
args: {
size: 'large',
children: 'Large Button',
},
};
export const Loading: Story = {
args: {
loading: true,
children: 'Loading...',
},
};
export const Disabled: Story = {
args: {
disabled: true,
children: 'Disabled',
},
};Button Test (src/components/Button/Button.test.tsx):
import { render, screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';
import { describe, it, expect, vi } from 'vitest';
import { Button } from './Button';
describe('Button', () => {
it('renders children correctly', () => {
render(<Button>Click me</Button>);
expect(screen.getByText('Click me')).toBeInTheDocument();
});
it('applies variant class', () => {
render(<Button variant="secondary">Button</Button>);
const button = screen.getByRole('button');
expect(button).toHaveClass('secondary');
});
it('handles click events', async () => {
const handleClick = vi.fn();
render(<Button onClick={handleClick}>Click</Button>);
await userEvent.click(screen.getByRole('button'));
expect(handleClick).toHaveBeenCalledTimes(1);
});
it('disables button when loading', () => {
render(<Button loading>Loading</Button>);
expect(screen.getByRole('button')).toBeDisabled();
});
it('disables button when disabled prop is true', () => {
render(<Button disabled>Disabled</Button>);
expect(screen.getByRole('button')).toBeDisabled();
});
});Phase 5: Build Configuration
I'll set up build configuration for library distribution:
Vite Config (vite.config.ts):
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';
import { resolve } from 'path';
import dts from 'vite-plugin-dts';
export default defineConfig({
plugins: [
react(),
dts({
insertTypesEntry: true,
include: ['src/**/*'],
exclude: ['**/*.test.tsx', '**/*.stories.tsx'],
}),
],
build: {
lib: {
entry: resolve(__dirname, 'src/index.ts'),
name: 'ComponentLibrary',
formats: ['es', 'cjs'],
fileName: (format) => `index.${format === 'es' ? 'mjs' : 'cjs'}`,
},
rollupOptions: {
external: ['react', 'react-dom'],
output: {
globals: {
react: 'React',
'react-dom': 'ReactDOM',
},
assetFileNames: 'assets/[name][extname]',
chunkFileNames: 'chunks/[name].[hash].js',
},
},
sourcemap: true,
emptyOutDir: true,
},
css: {
modules: {
localsConvention: 'camelCase',
},
},
});Package.json Configuration:
{
"name": "@your-org/component-library",
"version": "1.0.0",
"description": "A React component library",
"main": "./dist/index.cjs",
"module": "./dist/index.mjs",
"types": "./dist/index.d.ts",
"exports": {
".": {
"import": "./dist/index.mjs",
"require": "./dist/index.cjs",
"types": "./dist/index.d.ts"
},
"./styles": "./dist/style.css"
},
"files": [
"dist"
],
"scripts": {
"dev": "vite",
"build": "tsc && vite build",
"test": "vitest",
"test:ui": "vitest --ui",
"lint": "eslint src --ext ts,tsx",
"storybook": "storybook dev -p 6006",
"build-storybook": "storybook build",
"prepublishOnly": "npm run build"
},
"peerDependencies": {
"react": "^18.0.0",
"react-dom": "^18.0.0"
},
"devDependencies": {
"@storybook/react": "^7.6.0",
"@storybook/react-vite": "^7.6.0",
"@testing-library/react": "^14.0.0",
"@testing-library/user-event": "^14.0.0",
"@types/react": "^18.2.0",
"@vitejs/plugin-react": "^4.2.0",
"typescript": "^5.3.0",
"vite": "^5.0.0",
"vite-plugin-dts": "^3.7.0",
"vitest": "^1.0.0"
}
}TypeScript Configuration (tsconfig.json):
{
"compilerOptions": {
"target": "ES2020",
"useDefineForClassFields": true,
"lib": ["ES2020", "DOM", "DOM.Iterable"],
"module": "ESNext",
"skipLibCheck": true,
"moduleResolution": "bundler",
"allowImportingTsExtensions": true,
"resolveJsonModule": true,
"isolatedModules": true,
"noEmit": true,
"jsx": "react-jsx",
"strict": true,
"noUnusedLocals": true,
"noUnusedParameters": true,
"noFallthroughCasesInSwitch": true,
"declaration": true,
"declarationMap": true,
"sourceMap": true,
"baseUrl": ".",
"paths": {
"@/*": ["src/*"]
}
},
"include": ["src"],
"exclude": ["node_modules", "dist", "**/*.stories.tsx", "**/*.test.tsx"]
}Phase 6: Documentation Setup
I'll create comprehensive documentation:
README.md:
# Component Library
A modern React component library built with TypeScript, Storybook, and Vite.
## Installation
```bash
npm install @your-org/component-library
# or
yarn add @your-org/component-libraryUsage
import { Button } from '@your-org/component-library';
import '@your-org/component-library/styles';
function App() {
return (
<Button variant="primary" size="large">
Click me
</Button>
);
}Components
- Button - Versatile button component with variants and sizes
- Input - Form input with validation support
- Card - Container component for content
- [See full component list in Storybook]
Development
# Install dependencies
npm install
# Start Storybook
npm run storybook
# Run tests
npm test
# Build library
npm run buildContributing
See CONTRIBUTING.md for guidelines.
License
MIT
**Getting Started Guide (docs/getting-started.md):**
```markdown
# Getting Started
## Installation
Install the component library in your React project:
```bash
npm install @your-org/component-libraryBasic Setup
Import components and styles:
import { Button, Input, Card } from '@your-org/component-library';
import '@your-org/component-library/styles';TypeScript Support
The library is written in TypeScript and includes type definitions:
import type { ButtonProps } from '@your-org/component-library';
const MyButton: React.FC<{ onClick: () => void }> = ({ onClick }) => {
return <Button variant="primary" onClick={onClick}>Click</Button>;
};Theming
Customize component styles with CSS variables:
:root {
--primary-color: #007bff;
--secondary-color: #6c757d;
--border-radius: 4px;
}Next Steps
- Browse components in Storybook
- Read component documentation
- Check out examples
## Token Optimization
**Expected range**: 800–2,500 tokens (initial), 200 tokens (cache hit)
**Caching**: Caches component inventory in `.claude/cache/component_library/` for 7 days. Invalidated when component files change.
**Early exit**: Returns immediately if the requested component already exists in the library.
**Patterns used**: Grep-before-Read, early exit, template-based generation, cachingDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

