
Design System Documentation Generator
Generate production-ready design system documentation from tokens to components
What You Can Do
This skill generates structured, maintainable documentation that serves as your design system's single source of truth. You'll produce professional spec sheets, token architecture guides, component usage patterns, accessibility compliance requirements, and developer implementation guides—all formatted for different audiences from designers to engineers. It eliminates gaps between design intent and code by creating clear governance frameworks and contribution guidelines.
Features
Generate complete token inventories with naming conventions, semantic grouping, and usage context for colors, typography, spacing, and effects
Create detailed specs including anatomy, props, states, behavior definitions, and visual annotations for each component
Produce code-ready documentation with examples, integration patterns, and best practices for developer handoff
Document WCAG requirements, keyboard interactions, ARIA attributes, and testing criteria for each component
Generate design patterns, do's/don'ts, edge cases, and contextual usage recommendations for consistent application
Build frameworks defining component contribution criteria, update processes, and decision-making authority
Output documentation structured for designers (aesthetic rationale, visual patterns) and developers (precise specs, code examples)
Generate token relationships, component hierarchy, and dependency mappings for complex systems
Example Output
Design Token Documentation:
Color Tokens
├── Primary
│ ├── primary-50: #F0F7FF (Light backgrounds)
│ ├── primary-500: #0066CC (Interactive elements)
│ └── primary-900: #00264D (High contrast text)
├── Semantic
│ ├── background-default: {primary-50}
│ └── text-interactive: {primary-500}
Component Spec Example:
Button Component
- Variants: primary, secondary, tertiary, ghost
- States: default, hover, active, disabled, loading
- Props: size (sm/md/lg), icon, label, fullWidth
- Accessibility: role="button", keyboard navigation, focus states
- Code Example: <Button variant="primary" size="md">Click Me</Button>
Usage Guideline:
- ✅ Use primary buttons for main actions
- ❌ Don't combine two primary buttons in one interface
- ⚠️ Consider mobile touch targets (min 44px)
What's Included
- SKILL.md: Complete instruction file with token documentation templates
- Design Token Template: Structured format for token inventories, naming conventions, and semantic mappings
- Component Specification Checklist: Comprehensive breakdown covering anatomy, props, states, accessibility, and code examples
- Implementation Guide Framework: Developer-focused documentation structure with integration patterns and best practices
- Accessibility Compliance Matrix: WCAG requirements mapped to component states and interactions
- Contribution Guidelines Template: Governance framework for component submissions and system updates
Who It's For
- Design Systems Leads — Create authoritative documentation that unifies design and development teams
- UI/UX Designers — Document design decisions, token systems, and component patterns for cross-team collaboration
- Frontend Engineers — Access clear implementation specs, code examples, and accessibility requirements
- Design Operations Managers — Establish governance frameworks and contribution processes for scaling design systems
- Product Managers — Reference design rationale, decision frameworks, and compliance documentation
Best For
- Launching new design systems or major system expansions
- Documenting new component families and design tokens
- Creating developer handoff documentation to reduce implementation time
- Building onboarding materials for designers and engineers joining the system
- Establishing and maintaining design system governance and contribution standards
- Defining accessibility compliance across all components
- Creating multi-format documentation for different audiences







