color

Map functional roles to perceptual color values for WCAG 2.2 contrast compliance.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/loveconnor/clove-skills --skill color-loveconnor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: color
Source: https://github.com/loveconnor/clove-skills/tree/main/.agents/skills/color
Command: npx skills add https://github.com/loveconnor/clove-skills --skill color-loveconnor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the fragmentation and inaccessibility of color systems by providing a structured, role-based approach to palette design, theme management, and contrast verification.

Core Features & Use Cases

  • Semantic Tokenization: Map colors to functional roles like surface, text, and action rather than raw values.
  • Accessibility Auditing: Evaluate foreground/background pairs against WCAG 2.2 standards for various states and themes.
  • Theme Construction: Generate consistent light and dark mode mappings that maintain hierarchy and readability.
  • Use Case: When migrating a legacy UI to a modern design system, use this skill to audit existing hardcoded colors, define a new semantic token architecture, and verify contrast across all interactive states.

Quick Start

Use the color skill to audit the current interface for WCAG 2.2 contrast compliance and generate a semantic token mapping for light and dark themes.

Frequently Asked Questions about color

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

FAQPage Schema
How do I build a semantic color system for UI design?

To build a semantic color system, map raw perceptual color values to functional interface roles like surface, text, and action. This approach creates structured design tokens that maintain cross-theme consistency and hierarchy across light and dark modes.

How do I audit my interface for WCAG 2.2 contrast compliance?

You audit WCAG 2.2 contrast compliance by evaluating foreground and background color pairs against accessibility standards. This verifies readability across various interactive states and themes to ensure your digital interface is fully accessible.

What is the best way to migrate hardcoded UI colors to design tokens?

The best way to migrate hardcoded UI colors is to audit existing values, define a new semantic token architecture mapping colors to functional roles, and verify contrast across all interactive states for light and dark theme construction.

Can I generate consistent light and dark mode mappings with semantic tokens?

Yes, you can generate consistent light and dark mode mappings by mapping functional roles to perceptual color values. This maintains visual hierarchy and readability while ensuring cross-theme consistency across your design system.

Does this approach handle gamut management for data visualization palettes?

Yes, this approach handles gamut management and creates data visualization palettes. It maps functional roles to perceptual color values while satisfying WCAG 2.2 contrast compliance and cross-theme consistency requirements.

When should I not use raw color values in a design system?

You should not use raw color values when a UI requires accessibility verification, multiple themes, or interactive states. Raw values cause fragmentation; semantic tokens mapping to functional roles ensure cross-theme consistency instead.