color-system

Design semantic color roles, surface hierarchy, and light/dark themes from project context.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill color-system-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: color-system
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/color-system
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill color-system-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship arbitrary palettes or raw hex values that break hierarchy, accessibility, and dark mode. This Skill turns color into a structured system of semantic roles grounded in the existing project and platform design references. ## Core Features & Use Cases - Semantic role modeling: Define surface, content, action, feedback, and structural color roles before assigning raw values, separating primitives from semantic and component tokens. - Theme transformation: Build light/dark/high-contrast themes that preserve role relationships instead of simple inversion, with verification on representative rendered screens. - Brand and state allocation: Allocate brand accents to key actions and states without semantic collisions, and design hover/pressed/selected/disabled states as relationships to base roles. - Use Case: When redesigning a product UI, audit existing tokens, map them to semantic roles, consult Apple HIG, Material 3, Spectrum, and USWDS references, then verify hierarchy across light and dark rendered screens. ## Quick Start Use the color-system skill to audit my current color tokens and propose a semantic role structure with light and dark theme mappings.

Frequently Asked Questions about color-system

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

FAQPage Schema
How do I design a semantic color system for a web product?

Define roles before values: classify surface, content, action, feedback, and structural roles, then map primitive tokens to semantic tokens like surface/raised or action/primary. Verify the result on representative rendered screens in both light and dark themes.

How should I build a dark mode theme for my design system?

Do not invert the light palette. Check that surface hierarchy, text hierarchy, accent prominence, borders, and status colors are preserved, and confirm images, charts, and code surfaces fit the dark theme.

What design references inform this color system approach?

The Skill draws on Apple Human Interface Guidelines for color and branding, Material 3 color roles, Adobe Spectrum color fundamentals, and USWDS color tokens. It extracts role-pairing principles rather than copying exact color values.

When should I not use this color system skill?

Do not use it for detailed data visualization palette design; categorical, sequential, and diverging chart palettes belong to a dedicated data-visualization skill. It also defers token vocabulary drift audits to a token-audit skill.

How do I avoid brand color overuse in UI design?

Limit brand color to primary actions, selected states, brand-bearing content, and small signature moments. Avoid applying it to every button, icon, or border, and never let it collide with status color semantics.