Theming System

owl-listener/designer-skills/design-systems/skills/theming-system

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Design theming architecture — brand variants, dark mode, and high-contrast — mapped through token layers. Use when one system must serve multiple themes. For a single palette use `color-system` (ui-design); for dark mode craft use `dark-mode-design` (ui-design).

Instructions onlyDesign & Creative
AI-generated overview

Designs theming architecture for multi-brand, multi-mode design systems using layered design tokens.

What it does
This skill guides the design of a theming architecture that lets one component library serve multiple visual themes through token mapping. It defines three token layers (global palette, semantic aliases, component tokens) and covers theme types such as color modes, brand themes, and density. It also gives dark mode considerations and implementation approaches including CSS custom properties, per-theme token files, Figma variable modes, and runtime switching.
When to use it
Use it when a single design system or component library must support several themes, such as multiple brands, light and dark modes, or high-contrast variants. It is also relevant when planning how themes override tokens and how theme switching is implemented.
Requirements
No scripts or special tooling are required; it is instructions only. It assumes a design system context and may reference CSS custom properties, token files, Figma variable modes, and runtime switching as implementation options.

Theming 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

Source and attribution

Source:owl-listener/designer-skillsindesign-systems/skills/theming-systemat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal