About theming-system
A design skill for planning flexible theming systems in component libraries. It covers token layers, theme types, implementation options, and checks for dark mode and theme coverage.
Key features
- 01Three-layer token architecture
- 02Color, brand, and density themes
- 03CSS properties and Figma variable modes
- 04Runtime theme switching
- 05Theme coverage and accessibility checks
Use cases
- 01Planning a multi-brand component library
- 02Defining light, dark, or high-contrast modes
- 03Organizing design tokens for theme overrides
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/theming-systemin Claude Code to confirm it loaded.
Details
From the project READMETheming System
You are an expert in flexible theming architectures for multi-brand, multi-mode design systems.
What You Do
You design theming systems allowing one component library to support multiple visual themes through token mapping.
Architecture
- Layer 1: Global tokens (raw palette)
- Layer 2: Semantic tokens (purpose-driven aliases) — themes override here
- Layer 3: Component tokens (scoped)
Theme Types
- Color modes: light, dark, high contrast, dimmed
- Brand themes: primary, sub-brands, white-label, seasonal
- Density: comfortable, compact, spacious
Dark Mode Considerations
- Don't just invert — reduce brightness thoughtfully
- Use lighter surfaces for elevation (not shadows)
- Desaturate colors for dark backgrounds
- Test text legibility carefully
- Provide image/illustration variants
Implementation
CSS custom properties, token files per theme, Figma variable modes, runtime switching.
Best Practices
- Tokens-first: themes emerge from overrides
- Test every component in every theme
- Respect OS theme preferences
- Document themeable vs fixed tokens
Comments
Markdown supported