How do I install the Theme Parity skill?

Run npx skillmds@latest add abbaye/theme-parity in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Theme Parity safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Theme Parity?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Theme Parity free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Theme Parity?

abbaye (@abbaye) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Theme Parity by abbaye — Agent Skill

Name: Theme Parity
Author: abbaye

Theme Parity

INTERNAL DEV WORKFLOW for WpfHexEditor — Claude self-invokes after editing Themes/<Theme>/Colors.xaml or *Theme.xaml to verify the 18 themes share the same key surface. Detects: theme-key-missing (key in Dark but not in the edited theme), theme-key-orphan (key only in this theme), theme-color-no-brush (Color without paired SolidColorBrush), theme-merge-order (wrapper merges Colors.xaml after Menu.xaml/TabControl.xaml). Skip on: edits outside the Themes/ tree.

abbaye 3dc306e 4 files · 28.5 KB Updated Sep 17, 2026

File contents

theme-parity (internal)

Theme switching is a pure ResourceDictionary swap — every theme must expose the same key set. DarkTheme is the canonical reference.

When I invoke

Situation	Run?
Edit `*/Themes/<X>/Colors.xaml` (Shell or Docking)	yes
Edit `*Theme.xaml` wrapper (merge order)	yes
Add a new theme folder	yes (regen reference first)
Edit non-theme XAML	no (`xaml-guard` / `ui-design`)

Pipeline

If data/reference-keys.txt missing: scripts/theme-parity.ps1 -RefreshReference (extracts keys from Dark).
scripts/theme-parity.ps1 -Files <paths> → per-theme summary.
Suggest patch (copy-paste values from Dark): scripts/theme-parity.ps1 -Files <path> -SuggestPatch

4 rules

Rule	Severity	Detects
`theme-key-missing`	error	key in Dark reference, absent from edited theme
`theme-key-orphan`	warn	key only in edited theme, no other theme has it
`theme-color-no-brush`	warn	`<Color x:Key="XColor">` without paired `<SolidColorBrush x:Key="XBrush">`
`theme-merge-order`	error	`*Theme.xaml` merges Colors.xaml AFTER Menu.xaml/TabControl.xaml

Output

Theme: Cyberpunk
  Missing: 4   DockMenuHighlightColor, DockMenuHighlightBrush, DockSplitterColor, DockSplitterBrush
  Orphan:  1   CyberNeonAccentColor
  Color/brush mismatch: 0  |  Merge order: OK

Does not validate color aesthetics, auto-apply patches, or check token usage in non-theme XAML (ui-design covers that).

Maintenance

Adding keys to Dark → regen reference, then theme-parity.ps1 fires on all other themes to roll the token.
Promoting token to all themes → add to Dark first, regen, propagate.

---name: theme-paritydescription: INTERNAL DEV WORKFLOW for WpfHexEditor — Claude self-invokes after editing Themes/<Theme>/Colors.xaml or *Theme.xaml to verify the 18 themes share the same key surface. Detects: theme-key-missing (key in Dark but not in the edited theme), theme-key-orphan (key only in this theme), theme-color-no-brush (Color without paired SolidColorBrush), theme-merge-order (wrapper merges Colors.xaml after Menu.xaml/TabControl.xaml). Skip on: edits outside the Themes/ tree.---# theme-parity (internal)Theme switching is a pure ResourceDictionary swap — every theme must expose the same key set. `DarkTheme` is the canonical reference.## When I invoke| Situation | Run? ||---|---|| Edit `*/Themes/<X>/Colors.xaml` (Shell or Docking) | yes || Edit `*Theme.xaml` wrapper (merge order) | yes || Add a new theme folder | yes (regen reference first) || Edit non-theme XAML | no (`xaml-guard` / `ui-design`) |## Pipeline1. If `data/reference-keys.txt` missing: `scripts/theme-parity.ps1 -RefreshReference` (extracts keys from Dark).2. `scripts/theme-parity.ps1 -Files <paths>` → per-theme summary.3. Suggest patch (copy-paste values from Dark): `scripts/theme-parity.ps1 -Files <path> -SuggestPatch`## 4 rules| Rule | Severity | Detects ||---|---|---|| `theme-key-missing` | error | key in Dark reference, absent from edited theme || `theme-key-orphan` | warn | key only in edited theme, no other theme has it || `theme-color-no-brush` | warn | `<Color x:Key="XColor">` without paired `<SolidColorBrush x:Key="XBrush">` || `theme-merge-order` | error | `*Theme.xaml` merges Colors.xaml AFTER Menu.xaml/TabControl.xaml |## Output```Theme: Cyberpunk Missing: 4 DockMenuHighlightColor, DockMenuHighlightBrush, DockSplitterColor, DockSplitterBrush Orphan: 1 CyberNeonAccentColor Color/brush mismatch: 0 | Merge order: OK```Does not validate color aesthetics, auto-apply patches, or check token usage in non-theme XAML (`ui-design` covers that).## Maintenance- Adding keys to Dark → regen reference, then `theme-parity.ps1` fires on all other themes to roll the token.- Promoting token to all themes → add to Dark first, regen, propagate.

Frequently asked questions