What is the theming system skill?
The theming system skill is a short SKILL.md in the Owl-Listener designer skills repo, inside the design-systems plugin. It tells an AI coding agent to design theming through global, semantic and component token layers, so brand themes, dark mode and density modes override one layer.
It is a compact skill from the design-systems plugin of the designer skills collection. Its description is to design theming architecture, covering brand variants, dark mode and high contrast, mapped through token layers.
The core idea is that a theme should be an override, not a copy. Themes replace values at the semantic token layer, while components keep reading the same names and stay untouched.
What changes in your agent's output
- Tokens are split into global, semantic and component layers, and themes override only the semantic layer.
- Color modes, brand themes and density are treated as separate theme types, not one big switch.
- Dark mode is not an inversion: surfaces get lighter for elevation, colors are desaturated and text legibility is tested.
- Every component is expected to be tested in every theme, with themeable and fixed tokens documented.
Who it is for
Best for
- Teams that must ship one component library in several brand themes or white label variants.
- Developers adding dark mode and high contrast to an existing system through CSS custom properties.
- Projects that already use tokens and want rules for layering them, alongside design-token and color-system.
Not for
- Anyone who needs a single palette only. The description sends that job to color-system.
- Readers who want dark mode craft in depth, which the description sends to dark-mode-design.
- Teams wanting code. The file lists implementation options but gives no snippets.
Use it with UiChemy
Settle your theme tokens in the design, then use UiChemy Figma to WordPress to convert the finished design into an editable WordPress page. Click Get Started on uichemy.com.
How to install Theming System Skill: Brand Themes and Dark Mode via Tokens
/plugin marketplace add Owl-Listener/designer-skillsThe skill ships inside the design-systems plugin, so installing it brings the other skills in that plugin too.Add the marketplace
Run the command above in Claude Code. The README says this only registers where the skills live and nothing installs yet.
Install the design-systems plugin
Run /plugin install design-systems@designer-skills, or type /plugin, open the Discover tab and tick design-systems.
Gemini CLI route
The README says each plugin is also a Gemini CLI extension. Clone the repo and copy its .gemini/extensions folder into your project.
Ask for a theme plan
Ask the agent to design a theming architecture for light, dark and a second brand theme on your component library.
Check that it loaded
Ask the agent how to add a dark theme to a button. It should answer with a semantic token override instead of a separate dark button component.
Key features
- Three token layersGlobal tokens hold the raw palette, semantic tokens are purpose driven aliases that themes override, and component tokens are scoped.
- Color modesCovers light, dark, high contrast and dimmed modes as theme types.
- Brand themesCovers primary brands, sub brands, white label and seasonal themes on one component library.
- Density themesTreats comfortable, compact and spacious density as a theme type alongside color and brand.
- Dark mode rulesDo not just invert, reduce brightness, use lighter surfaces for elevation, desaturate colors and test text legibility.
- Image variantsAsks for image and illustration variants for dark backgrounds, not only color tokens.
- Implementation optionsNames CSS custom properties, token files per theme, Figma variable modes and runtime switching.
- Tokens firstBest practices say themes should emerge from overrides, so components are not rewritten per theme.
- Test every themeEvery component is tested in every theme, and OS theme preferences are respected.
- Document what is fixedCalls for documenting which tokens are themeable and which are fixed.
Frequently asked questions
What is the theming system skill?
It is a SKILL.md from the Owl-Listener designer skills repo, in the design-systems plugin. It guides an AI coding agent to design theming with global, semantic and component token layers so one library supports many themes.
How do I install the theming system skill?
Run /plugin marketplace add Owl-Listener/designer-skills in Claude Code, then /plugin install design-systems@designer-skills. The README also describes a Gemini CLI extension route that copies the repo's .gemini extensions folder into your project.
Which token layer do themes change?
The skill says layer two, the semantic tokens, is where themes override. Global tokens stay as the raw palette and component tokens stay scoped, so components keep reading the same names across every theme.
What theme types does it cover?
Color modes such as light, dark, high contrast and dimmed. Brand themes such as primary, sub brands, white label and seasonal. Density themes such as comfortable, compact and spacious. Each is handled through token mapping.
Does it explain how to build dark mode?
It gives short rules: do not just invert, use lighter surfaces for elevation, desaturate colors and test legibility. For deeper craft its description points to dark-mode-design, which is a separate skill in the same repo.
How is it different from a color skill?
A color skill builds one palette. This skill decides how many palettes and modes plug into the same components. Its description points single palette work to color-system instead, so use that first when you only need one palette.
Can I use it with Cursor or Codex?
The README names Claude Code and Gemini CLI as the supported tools. For other agents you could copy the SKILL.md text into that tool's rules, but the repo does not document that route.
What are the limits of this skill?
It is a short rule list, not a code generator. It names implementation options like CSS custom properties and Figma variable modes but gives no snippets, so pair it with design-system-patterns or your own token files.


