Provides guidelines for using color in design. Use when discussing color schemes, accessibility, or visual hierarchy.
Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.
You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and especially existing brand colors.
Attempt to gather these from the current thread or codebase.
Do NOT proceed until you have answers. Guessing leads to generic AI slop colors.
Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts.
Analyze the current state and identify opportunities:
Understand current state:
Identify where color adds value:
If any of these are unclear from the codebase, {{ask_instruction}}
CRITICAL: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose.
Create a purposeful color introduction plan:
IMPORTANT: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more.
Add color systematically across these dimensions:
State indicators:
Status badges: Colored backgrounds or borders for states (active, pending, completed, etc.)
Progress indicators: Colored bars, rings, or charts showing completion or health
#f5f5f5) with warm neutrals (oklch(97% 0.01 60)) or cool tints (oklch(97% 0.01 250))Use OKLCH for color: It's perceptually uniform, meaning equal steps in lightness look equal. Great for generating harmonious scales.
Ensure color addition improves rather than overwhelms:
NEVER:
#000) or pure white (#fff) for large areasTest that colorization improves the experience:
Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional.