create-style-guide
Generate comprehensive style guide documentation from theme and design tokens. Outputs to markdown, HTML, or Figma tokens.
What this skill does
# Create Style Guide Command
Generate comprehensive style guide documentation from design tokens and theme configuration.
## Usage
```bash
/cms:create-style-guide --format markdown
/cms:create-style-guide --format html --include all
/cms:create-style-guide --format figma-tokens
```
## Format Options
- **markdown**: Markdown documentation
- **html**: Interactive HTML style guide
- **figma-tokens**: Figma Tokens plugin format
## Workflow
### Step 1: Parse Arguments
Extract format and include options from command.
### Step 2: Load Design Tokens
Read existing design tokens from:
- Token JSON files
- CSS variable definitions
- Theme configuration
### Step 3: Invoke Skills
Invoke relevant skills:
- `design-token-management` - Token analysis
- `multi-site-theming` - Theme variations
### Step 4: Generate Markdown Style Guide
```markdown
# Design System Style Guide
## Table of Contents
1. [Brand Overview](#brand-overview)
2. [Colors](#colors)
3. [Typography](#typography)
4. [Spacing](#spacing)
5. [Components](#components)
6. [Icons](#icons)
7. [Usage Guidelines](#usage-guidelines)
---
## Brand Overview
### Brand Values
- **Professional**: Clean, trustworthy, reliable
- **Modern**: Contemporary, innovative, forward-thinking
- **Accessible**: Inclusive, clear, easy to use
### Voice & Tone
- Clear and concise
- Friendly but professional
- Action-oriented
---
## Colors
### Primary Colors
| Name | Hex | RGB | CSS Variable |
|------|-----|-----|--------------|
| Brand Primary | #2563eb | rgb(37, 99, 235) | `--color-brand-primary` |
| Brand Dark | #1e40af | rgb(30, 64, 175) | `--color-brand-dark` |
| Brand Light | #93c5fd | rgb(147, 197, 253) | `--color-brand-light` |
### Neutral Colors
| Name | Hex | Usage |
|------|-----|-------|
| Gray 50 | #f9fafb | Backgrounds |
| Gray 100 | #f3f4f6 | Subtle backgrounds |
| Gray 500 | #6b7280 | Secondary text |
| Gray 900 | #111827 | Primary text |
### Semantic Colors
| Name | Color | Usage |
|------|-------|-------|
| Success | #22c55e | Confirmations, positive states |
| Warning | #f59e0b | Cautions, important notices |
| Error | #ef4444 | Errors, destructive actions |
| Info | #3b82f6 | Informational messages |
### Color Usage Guidelines
**Do:**
- Use brand primary for CTAs and key actions
- Use semantic colors consistently for their intended purpose
- Ensure 4.5:1 contrast ratio for text
**Don't:**
- Use brand colors for error states
- Mix semantic colors outside their purpose
- Use low-contrast color combinations
---
## Typography
### Font Families
| Purpose | Font | Fallback |
|---------|------|----------|
| Headings | Inter | system-ui, sans-serif |
| Body | Inter | system-ui, sans-serif |
| Code | JetBrains Mono | monospace |
### Type Scale
| Name | Size | Line Height | Usage |
|------|------|-------------|-------|
| Display | 3.815rem | 1.1 | Hero headlines |
| H1 | 3.052rem | 1.2 | Page titles |
| H2 | 2.441rem | 1.2 | Section titles |
| H3 | 1.953rem | 1.3 | Subsections |
| H4 | 1.563rem | 1.3 | Card titles |
| Body | 1rem | 1.6 | Paragraph text |
| Small | 0.8rem | 1.5 | Captions, labels |
### Text Styles
#### Headings
```html
<h1 class="text-h1">Page Title</h1>
<h2 class="text-h2">Section Title</h2>
<h3 class="text-h3">Subsection</h3>
```
#### Body Text
```html
<p class="text-body">Regular paragraph text</p>
<p class="text-lead">Introductory paragraph with emphasis</p>
<p class="text-small">Caption or helper text</p>
```
---
## Spacing
### Spacing Scale
| Token | Value | Usage |
|-------|-------|-------|
| space-1 | 0.25rem | Tight padding |
| space-2 | 0.5rem | Element padding |
| space-4 | 1rem | Component padding |
| space-8 | 2rem | Section gaps |
| space-16 | 4rem | Large gaps |
### Layout Guidelines
- Use `space-4` for standard component padding
- Use `space-8` between related sections
- Use `space-16` between major page sections
---
## Components
### Buttons
#### Primary Button
```html
<button class="btn btn-primary">Primary Action</button>
```
- Use for main CTA
- One primary button per section
#### Secondary Button
```html
<button class="btn btn-secondary">Secondary Action</button>
```
- Use for alternative actions
- Can pair with primary button
#### Button States
| State | Description |
|-------|-------------|
| Default | Normal resting state |
| Hover | Darkened background |
| Active | Further darkened |
| Disabled | 50% opacity, no pointer |
### Cards
```html
<div class="card">
<img class="card-image" src="..." alt="...">
<div class="card-content">
<h3 class="card-title">Title</h3>
<p class="card-description">Description</p>
</div>
</div>
```
### Form Elements
#### Text Input
```html
<label class="label" for="email">Email</label>
<input type="email" id="email" class="input" placeholder="[email protected]">
```
#### Validation States
| State | Border Color | Icon |
|-------|--------------|------|
| Default | Gray 300 | None |
| Focus | Brand Primary | None |
| Error | Error Red | Error icon |
| Success | Success Green | Check icon |
---
## Icons
### Icon System
- **Library**: Lucide Icons
- **Size**: 24px default
- **Stroke**: 2px
### Common Icons
| Icon | Name | Usage |
|------|------|-------|
| ➕ | plus | Add actions |
| ✏️ | edit | Edit actions |
| 🗑️ | trash | Delete actions |
| ✓ | check | Success, complete |
| ✕ | x | Close, cancel |
---
## Usage Guidelines
### Accessibility Checklist
- [ ] Color contrast meets WCAG AA (4.5:1)
- [ ] Text can scale to 200%
- [ ] Interactive elements have focus states
- [ ] Icons have accessible labels
### Responsive Breakpoints
| Name | Min Width | Usage |
|------|-----------|-------|
| mobile | 0 | Mobile-first base |
| tablet | 768px | Tablet and up |
| desktop | 1024px | Desktop and up |
| wide | 1280px | Large screens |
### Performance Guidelines
- Use system fonts for body text when possible
- Lazy load images below the fold
- Limit custom fonts to 2-3 families
### Step 5: Generate Figma Tokens (if format=figma-tokens)
**Figma Tokens Format:**
```json
{
"global": {
"colors": {
"brand": {
"primary": {
"value": "#2563eb",
"type": "color"
},
"secondary": {
"value": "#93c5fd",
"type": "color"
}
},
"gray": {
"50": { "value": "#f9fafb", "type": "color" },
"100": { "value": "#f3f4f6", "type": "color" },
"500": { "value": "#6b7280", "type": "color" },
"900": { "value": "#111827", "type": "color" }
}
},
"typography": {
"fonts": {
"heading": { "value": "Inter", "type": "fontFamilies" },
"body": { "value": "Inter", "type": "fontFamilies" }
},
"fontSizes": {
"xs": { "value": "10", "type": "fontSizes" },
"sm": { "value": "12", "type": "fontSizes" },
"base": { "value": "16", "type": "fontSizes" },
"lg": { "value": "20", "type": "fontSizes" },
"xl": { "value": "25", "type": "fontSizes" }
},
"fontWeights": {
"normal": { "value": "400", "type": "fontWeights" },
"medium": { "value": "500", "type": "fontWeights" },
"bold": { "value": "700", "type": "fontWeights" }
}
},
"spacing": {
"1": { "value": "4", "type": "spacing" },
"2": { "value": "8", "type": "spacing" },
"4": { "value": "16", "type": "spacing" },
"8": { "value": "32", "type": "spacing" }
},
"borderRadius": {
"sm": { "value": "2", "type": "borderRadius" },
"md": { "value": "6", "type": "borderRadius" },
"lg": { "value": "8", "type": "borderRadius" },
"full": { "value": "9999", "type": "borderRadius" }
}
},
"$themes": [
{
"id": "light",
"name": "Light",
"selectedTokenSets": {
"global": "enabled"
}
}
]
}
```
### Step 6: Generate HTML Style Guide (if format=html)
Interactive HTML output with:
- Live color swatches
- Typography specimens
- Component playgrounRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.