
Design System Creation
- 381 installs
- 202 repo stars
- Updated August 4, 2026
- secondsky/claude-skills
design-system-creation is a Claude Code skill that creates comprehensive design systems with typography, colors, components, and documentation for developers establishing cross-team UI standards, component libraries, and
About
design-system-creation is a skill in secondsky/claude-skills that produces full design system packages for consistent UI development. It covers design tokens, typography scales, spacing, semantic color palettes, dark mode theming, CSS variables, responsive grid breakpoints, WCAG accessibility, component patterns, and supporting documentation aligned with Figma and Storybook workflows. Developers invoke it when standing up a new product UI foundation, formalizing brand rules, or preventing one-off styling drift across repositories. The skill emphasizes semantic tokens, component libraries, and style guides developers can hand to implementation teams.
- Extends Claude Code agent capabilities
- Activates on relevant task triggers
- Integrates with Claude Code workflow
Design System Creation by the numbers
- 381 all-time installs (skills.sh)
- +14 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #2,050 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/secondsky/claude-skills --skill design-system-creationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 381 |
|---|---|
| repo stars | ★ 202 |
| Last updated | August 4, 2026 |
| Repository | secondsky/claude-skills ↗ |
How do you create a design system with tokens and components?
design-system-creation: agent skill for task automation in Claude Code workflows.
Who is it for?
Frontend leads defining reusable tokens, components, and documentation before scaling UI work across multiple codebases or contributors.
Skip if: One-off page mockups or projects that only need a single component tweak without system-wide standards.
When should I use this skill?
The user asks to build or document a design system, define design tokens, create a component library, or enforce cross-team UI consistency.
What you get
Design token definitions, component specs, theming rules, accessibility guidance, and design system documentation.
- Design tokens
- Component documentation
- Style guide
By the numbers
- Metadata lists 20+ design-system keyword areas including tokens, WCAG, Storybook, and Figma
Files
Design System Creation
Build comprehensive design systems for consistent UI development across teams.
Design System Layers
1. Foundation: Colors, typography, spacing, elevation 2. Components: Buttons, inputs, cards, navigation 3. Patterns: Forms, layouts, empty states
Foundation - Design Tokens
:root {
/* Colors */
--color-primary-50: #eff6ff;
--color-primary-500: #3b82f6;
--color-primary-900: #1e3a8a;
/* Semantic colors */
--color-success: #22c55e;
--color-warning: #f59e0b;
--color-error: #ef4444;
/* Typography */
--font-sans: 'Inter', system-ui, sans-serif;
--font-mono: 'Fira Code', monospace;
/* Type scale */
--text-xs: 0.75rem;
--text-sm: 0.875rem;
--text-base: 1rem;
--text-lg: 1.125rem;
--text-xl: 1.25rem;
--text-2xl: 1.5rem;
/* Spacing (4px base) */
--space-1: 0.25rem;
--space-2: 0.5rem;
--space-4: 1rem;
--space-8: 2rem;
/* Elevation */
--shadow-sm: 0 1px 2px rgba(0,0,0,0.05);
--shadow-md: 0 4px 6px rgba(0,0,0,0.1);
--shadow-lg: 0 10px 15px rgba(0,0,0,0.1);
}Component Documentation
## Button
### Anatomy
- Container (padding, background)
- Label (text)
- Icon (optional)
### Variants
- Primary: Main actions
- Secondary: Alternative actions
- Ghost: Subtle actions
### States
- Default, Hover, Active, Disabled, Loading
### Accessibility
- Role: button
- Keyboard: Enter/Space to activate
- Focus: Visible focus ringComponent Example (React)
interface ButtonProps {
variant?: 'primary' | 'secondary' | 'ghost';
size?: 'sm' | 'md' | 'lg';
loading?: boolean;
disabled?: boolean;
children: React.ReactNode;
}
function Button({ variant = 'primary', size = 'md', loading, disabled, children }: ButtonProps) {
return (
<button
className={`btn btn-${variant} btn-${size}`}
disabled={disabled || loading}
aria-busy={loading}
>
{loading ? <Spinner /> : children}
</button>
);
}Governance
- Review Committee: Approves new components
- Contribution Process: RFC → Review → Implementation
- Versioning: Semantic versioning for releases
- Deprecation: 3-month notice with migration guide
Best Practices
- Start with foundational tokens
- Document every component thoroughly
- Ensure WCAG 2.1 AA compliance
- Support dark mode from the start
- Include usage guidelines with do/don't examples
Related skills
How it compares
Use design-system-creation for full token and component standards; use a single-component frontend skill when only one React pattern needs refinement.
FAQ
What does design-system-creation include?
design-system-creation covers typography, colors, spacing, components, patterns, CSS variables, dark mode, responsive breakpoints, WCAG accessibility, and documentation for consistent UI development across teams.
Does design-system-creation support component library tooling?
Yes. design-system-creation references Figma and Storybook in its metadata keywords, producing tokens and component documentation suitable for design-to-code handoff and library publishing.
When should teams use design-system-creation?
Teams should use design-system-creation when establishing design standards, building a component library, or ensuring cross-team UI consistency instead of letting each feature define its own styles.