ux-color-system

Map color theming problems to semantic CSS variables for fantasy UI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/matthewharwood/fantasy-phonics --skill ux-color-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-color-system
Source: https://github.com/matthewharwood/fantasy-phonics/tree/main/.claude/skills/ux-color-system
Command: npx skills add https://github.com/matthewharwood/fantasy-phonics --skill ux-color-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides semantic color tokens for fantasy-themed UI with accessibility checks and dark theme patterns.

Core Features & Use Cases

  • Semantic Tokens: surface, on-surface, primary, success, error
  • Usage Patterns: pairing surface/text, state colors, phase colors
  • Overlay & Gradients: color usage for hover, backgrounds, and emphasis
  • Color Accessibility: contrast rules and safe usage
  • Dark Theme: patterns for light/dark surfaces

Quick Start

Define CSS variables like --theme-surface and --color-success and apply to components.

Frequently Asked Questions about ux-color-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement accessible color tokens for a fantasy-themed UI?

Semantic color tokens map theming problems to CSS variables enforcing contrast and accessibility rules. Define tokens like --theme-surface, --color-success, and --color-error, then pair them with text colors (on-surface) to maintain WCAG contrast standards across light and dark themes for fantasy or medieval designs.

What's the best way to handle dark theme color pairing without manual adjustments?

Use semantic surface and text token pairs designed for both light and dark modes. The Skill provides predefined patterns for surface/text combinations and state colors that automatically maintain accessibility across theme switches, eliminating manual contrast recalculation.

Can I use CSS variables for fantasy UI color theming with accessibility checks?

Yes. CSS custom properties like --theme-surface, --color-primary, and feedback colors (success, error) integrate with accessibility contrast rules. The approach defines semantic tokens that enforce safe pairings, overlays, and phase indicators while supporting both light and dark surfaces.

How do I define color overlays and gradients while maintaining contrast standards?

Semantic token patterns include overlay and gradient definitions with built-in contrast enforcement. Map overlay usage to hover states and emphasis areas, then apply gradient patterns as CSS variables tied to surface and accent colors, ensuring accessibility across all interactive states.

What color tokens do I need for state indicators and phase markers in a design system?

Semantic tokens cover primary, secondary, success, and error states, plus phase indicators for multi-step workflows. The system provides CSS variables for each state and phase, with contrast rules ensuring text readability and accessible feedback colors across fantasy-themed interfaces.

Do I need a design system framework to use semantic color tokens?

No framework dependency required. Semantic color tokens work as standalone CSS custom properties applicable to any component or HTML structure. Define surface, text, state, and overlay variables, then apply them directly to your fantasy UI—no build tools or additional dependencies needed.