design system patterns

Design Community

Skill notes

When to Use This Skill

Creating design tokens for colors, typography, spacing, and shadows Implementing light/dark theme switching with CSS custom properties Building multi-brand theming systems Architecting component libraries with consistent APIs Establishing design-to-code workflows with Figma tokens

1. Design Tokens

Primitive tokens (raw values: colors, sizes, fonts) Semantic tokens (contextual meaning: text-primary, surface-elevated) Component tokens (specific usage: button-bg, card-border) Token naming conventions and organization Multi-platform token generation (CSS, iOS, Android)

2. Theming Infrastructure

CSS custom properties architecture Theme context providers in React Dynamic theme switching System preference detection (prefers-color-scheme) Persistent theme storage

3. Component Architecture

Compound component patterns Polymorphic components (as prop) Variant and size systems Slot-based composition Headless UI patterns

4. Token Pipeline

Figma to code synchronization Style Dictionary configuration Token transformation and formatting CI/CD integration for token updates

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@wshobson · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview design-system-patterns.preview
# Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.