design-systems
# Design Systems Skill
What this skill does
# Design Systems Skill
```yaml
name: design-systems-expert
risk_level: LOW
description: Expert in token-based theming, component APIs, design system architecture, and creating scalable design foundations
version: 1.0.0
author: JARVIS AI Assistant
tags: [design-system, tokens, theming, components, architecture]
```
---
## 1. Overview
**Risk Level**: LOW-RISK
**Justification**: Design systems produce CSS, design tokens, and component specifications without direct code execution or data processing.
You are an expert in **design system architecture**. You create scalable, maintainable design foundations with token-based theming, consistent component APIs, and clear documentation.
### Core Expertise
- Design token architecture
- Component API design
- Theme switching
- Documentation systems
- Version management
### Primary Use Cases
- Creating design system foundations
- Building component libraries
- Implementing theming systems
- Design system documentation
---
## 2. Core Responsibilities
### Fundamental Duties
1. **Token Architecture**: Build scalable token hierarchies
2. **Component Design**: Create consistent, composable components
3. **Theme Support**: Enable multiple themes
4. **Documentation**: Keep system well-documented
### Design System Principles
- **TDD First**: Write tests for tokens and components before implementation
- **Performance Aware**: Optimize CSS delivery, minimize repaints
- **Single source of truth**: Tokens define all values
- **Composability**: Components combine simply
- **Consistency**: Same patterns throughout
- **Extensibility**: Easy to extend, hard to break
---
## 3. Technical Foundation
### Token Hierarchy
```
┌─────────────────────────────────────┐
│ Semantic Tokens │
│ (purpose-specific references) │
│ --color-text-primary │
│ --color-bg-surface │
│ --spacing-component │
└──────────────┬──────────────────────┘
│ references
┌──────────────▼──────────────────────┐
│ Core Tokens │
│ (raw design values) │
│ --color-blue-500 │
│ --space-4 │
│ --font-size-base │
└─────────────────────────────────────┘
```
---
## 4. Implementation Patterns
### 4.1 Token Architecture
```css
/* tokens/core.css - Raw values */
:root {
/* Colors - Gray scale */
--color-gray-50: #f9fafb;
--color-gray-500: #6b7280;
--color-gray-900: #111827;
/* ... gray-100 through gray-800 */
/* Colors - Blue scale */
--color-blue-500: #3b82f6;
--color-blue-600: #2563eb;
/* Spacing (8px base): --space-0 through --space-16 */
--space-4: 1rem;
--space-6: 1.5rem;
/* Typography */
--font-size-base: 1rem;
--font-weight-medium: 500;
--line-height-normal: 1.5;
/* Radii */
--radius-md: 0.375rem;
--radius-lg: 0.5rem;
/* Shadows */
--shadow-md: 0 4px 6px rgba(0, 0, 0, 0.1);
}
```
```css
/* tokens/semantic.css - Purpose-specific */
:root {
/* Background */
--color-bg-primary: var(--color-white);
--color-bg-secondary: var(--color-gray-50);
/* Text */
--color-text-primary: var(--color-gray-900);
--color-text-secondary: var(--color-gray-600);
/* Border & Interactive */
--color-border-default: var(--color-gray-200);
--color-interactive-primary: var(--color-blue-600);
/* Component spacing */
--spacing-component-md: var(--space-3);
--spacing-component-lg: var(--space-4);
}
```
### 4.2 Theme Switching
```css
/* themes/light.css */
:root,
[data-theme="light"] {
--color-bg-primary: var(--color-white);
--color-text-primary: var(--color-gray-900);
--color-border-default: var(--color-gray-200);
}
/* themes/dark.css */
[data-theme="dark"] {
--color-bg-primary: var(--color-gray-900);
--color-text-primary: var(--color-gray-50);
--color-border-default: var(--color-gray-700);
}
```
```typescript
// Theme switcher (condensed)
function ThemeProvider({ children }: Props) {
const [theme, setTheme] = useState<"light" | "dark">("light");
useEffect(() => {
const saved = localStorage.getItem("theme") as "light" | "dark" | null;
const prefersDark = window.matchMedia("(prefers-color-scheme: dark)");
setTheme(saved || (prefersDark.matches ? "dark" : "light"));
}, []);
useEffect(() => {
document.documentElement.dataset.theme = theme;
}, [theme]);
const toggle = () => {
const next = theme === "light" ? "dark" : "light";
setTheme(next);
localStorage.setItem("theme", next);
};
return (
<ThemeContext.Provider value={{ theme, toggle }}>
{children}
</ThemeContext.Provider>
);
}
```
### 4.3 Component API Design
```typescript
// Consistent prop patterns
interface ButtonProps {
variant?: "primary" | "secondary" | "ghost" | "danger";
size?: "sm" | "md" | "lg";
disabled?: boolean;
loading?: boolean;
children: ReactNode;
onClick?: () => void;
}
function Button({ variant = "primary", size = "md", ...props }: ButtonProps) {
return (
<button
className={cn("button", `button--${variant}`, `button--${size}`)}
disabled={props.disabled || props.loading}
onClick={props.onClick}
>
{props.children}
</button>
);
}
```
### 4.4 Composition Patterns
```typescript
// Compound components
function Card({ children }: { children: ReactNode }) {
return <div className="card">{children}</div>;
}
Card.Header = ({ children }) => <div className="card-header">{children}</div>;
Card.Body = ({ children }) => <div className="card-body">{children}</div>;
Card.Footer = ({ children }) => <div className="card-footer">{children}</div>;
// Usage: <Card><Card.Header>Title</Card.Header><Card.Body>...</Card.Body></Card>
```
### 4.5 Token Export Formats
```typescript
// Export tokens in multiple formats
const tokens = {
colors: { primary: "#3b82f6", secondary: "#6b7280" },
spacing: { sm: "8px", md: "16px", lg: "24px" }
};
// CSS Custom Properties
function toCSS(tokens: Tokens): string {
let css = ":root {\n";
for (const [category, values] of Object.entries(tokens)) {
for (const [key, value] of Object.entries(values))
css += ` --${category}-${key}: ${value};\n`;
}
return css + "}";
}
// Tailwind config
function toTailwind(tokens: Tokens): TailwindConfig {
return { theme: { extend: { colors: tokens.colors, spacing: tokens.spacing } } };
}
```
---
## 5. Quality Standards
### Naming Conventions
- **Core tokens**: `--{category}-{scale}` (e.g., `--color-blue-500`)
- **Semantic tokens**: `--{category}-{property}-{variant}` (e.g., `--color-text-primary`)
- **Component tokens**: `--{component}-{property}-{state}` (e.g., `--button-bg-hover`)
### Documentation Requirements
- Token values with visual examples
- Component props and variants
- Usage guidelines and examples
- Do's and Don'ts
- Accessibility notes
---
## 6. Implementation Workflow (TDD)
### Step 1: Write Failing Test First
```typescript
// tests/tokens.test.ts
import { describe, it, expect } from 'vitest'
import { tokens } from '../tokens'
describe('Design Tokens', () => {
it('should have all required color scales', () => {
expect(tokens.colors.gray).toBeDefined()
expect(tokens.colors.blue).toBeDefined()
expect(Object.keys(tokens.colors.gray)).toHaveLength(10)
})
it('should have semantic tokens referencing core tokens', () => {
expect(tokens.semantic.textPrimary).toBe(tokens.colors.gray[900])
expect(tokens.semantic.bgPrimary).toBe(tokens.colors.white)
})
it('should generate valid CSS custom properties', () => {
const css = tokens.toCSS()
expect(css).toContain('--color-gray-500')
expect(css).toContain('--color-text-primary')
})
})
// tests/components/Button.test.ts
import { mount } from '@vue/test-utils'
import { describe, it, expect } from 'vitest'
import Button from '../components/Button.vue'
describe('Button', () => {
it('applies variant classes correctly', () => {
const wrapper = mount(BRelated 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.