home / skills / steveclarke / dotfiles / colorize

colorize skill

/ai/skills/colorize

This skill helps you strategically apply color to monochromatic interfaces, enhancing hierarchy, meaning, and warmth for better user engagement.

This is most likely a fork of the colorize skill from pbakaus
npx playbooks add skill steveclarke/dotfiles --skill colorize

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
6.7 KB
---
name: colorize
description: Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.
user-invokable: true
args:
  - name: target
    description: The feature or component to colorize (optional)
    required: false
---

Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.

## MANDATORY PREPARATION

Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: existing brand colors.

---

## Assess Color Opportunity

Analyze the current state and identify opportunities:

1. **Understand current state**:
   - **Color absence**: Pure grayscale? Limited neutrals? One timid accent?
   - **Missed opportunities**: Where could color add meaning, hierarchy, or delight?
   - **Context**: What's appropriate for this domain and audience?
   - **Brand**: Are there existing brand colors we should use?

2. **Identify where color adds value**:
   - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue)
   - **Hierarchy**: Drawing attention to important elements
   - **Categorization**: Different sections, types, or states
   - **Emotional tone**: Warmth, energy, trust, creativity
   - **Wayfinding**: Helping users navigate and understand structure
   - **Delight**: Moments of visual interest and personality

If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify.

**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose.

## Plan Color Strategy

Create a purposeful color introduction plan:

- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals)
- **Dominant color**: Which color owns 60% of colored elements?
- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%)
- **Application strategy**: Where does each color appear and why?

**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more.

## Introduce Color Strategically

Add color systematically across these dimensions:

### Semantic Color
- **State indicators**:
  - Success: Green tones (emerald, forest, mint)
  - Error: Red/pink tones (rose, crimson, coral)
  - Warning: Orange/amber tones
  - Info: Blue tones (sky, ocean, indigo)
  - Neutral: Gray/slate for inactive states

- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.)
- **Progress indicators**: Colored bars, rings, or charts showing completion or health

### Accent Color Application
- **Primary actions**: Color the most important buttons/CTAs
- **Links**: Add color to clickable text (maintain accessibility)
- **Icons**: Colorize key icons for recognition and personality
- **Headers/titles**: Add color to section headers or key labels
- **Hover states**: Introduce color on interaction

### Background & Surfaces
- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`)
- **Colored sections**: Use subtle background colors to separate areas
- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue)
- **Cards & surfaces**: Tint cards or surfaces slightly for warmth

**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales.

### Data Visualization
- **Charts & graphs**: Use color to encode categories or values
- **Heatmaps**: Color intensity shows density or importance
- **Comparison**: Color coding for different datasets or timeframes

### Borders & Accents
- **Accent borders**: Add colored left/top borders to cards or sections
- **Underlines**: Color underlines for emphasis or active states
- **Dividers**: Subtle colored dividers instead of gray lines
- **Focus rings**: Colored focus indicators matching brand

### Typography Color
- **Colored headings**: Use brand colors for section headings (maintain contrast)
- **Highlight text**: Color for emphasis or categories
- **Labels & tags**: Small colored labels for metadata or categories

### Decorative Elements
- **Illustrations**: Add colored illustrations or icons
- **Shapes**: Geometric shapes in brand colors as background elements
- **Gradients**: Colorful gradient overlays or mesh backgrounds
- **Blobs/organic shapes**: Soft colored shapes for visual interest

## Balance & Refinement

Ensure color addition improves rather than overwhelms:

### Maintain Hierarchy
- **Dominant color** (60%): Primary brand color or most used accent
- **Secondary color** (30%): Supporting color for variety
- **Accent color** (10%): High contrast for key moments
- **Neutrals** (remaining): Gray/black/white for structure

### Accessibility
- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components)
- **Don't rely on color alone**: Use icons, labels, or patterns alongside color
- **Test for color blindness**: Verify red/green combinations work for all users

### Cohesion
- **Consistent palette**: Use colors from defined palette, not arbitrary choices
- **Systematic application**: Same color meanings throughout (green always = success)
- **Temperature consistency**: Warm palette stays warm, cool stays cool

**NEVER**:
- Use every color in the rainbow (choose 2-4 colors beyond neutrals)
- Apply color randomly without semantic meaning
- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead
- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication
- Use pure black (`#000`) or pure white (`#fff`) for large areas
- Violate WCAG contrast requirements
- Use color as the only indicator (accessibility issue)
- Make everything colorful (defeats the purpose)
- Default to purple-blue gradients (AI slop aesthetic)

## Verify Color Addition

Test that colorization improves the experience:

- **Better hierarchy**: Does color guide attention appropriately?
- **Clearer meaning**: Does color help users understand states/categories?
- **More engaging**: Does the interface feel warmer and more inviting?
- **Still accessible**: Do all color combinations meet WCAG standards?
- **Not overwhelming**: Is color balanced and purposeful?

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.

Overview

This skill adds strategic color to interfaces that feel too gray or lifeless, making them more engaging, expressive, and usable. It focuses on purposeful palette selection, semantic color mapping, and subtle surface tints rather than indiscriminate saturation. The goal is clearer hierarchy, better meaning, and a warmer visual tone while preserving accessibility.

How this skill works

The skill inspects the current interface state (grayscale extent, existing neutrals, timid accents) and identifies concrete opportunities for color: semantic states, CTAs, headers, icons, backgrounds, charts, and dividers. It requires gathering brand context and executes a frontend-design analysis first to extract DOs and DON'Ts. Then it produces a 2–4 color palette in OKLCH, a dominant/secondary/accent split, and an application plan mapping each color to UI roles with accessibility checks.

When to use it

  • Interface feels monochrome or visually flat
  • You need to add semantic signaling (error/success/warning/info)
  • Launch or refresh of a product surface (dashboard, admin, marketing)
  • Improve visual hierarchy for CTAs, badges, or charts
  • Introduce warmth or personality without rebranding

Best practices

  • Collect explicit context first: target audience, brand personality, and existing brand colors
  • Run the frontend-design analysis before choosing colors to learn constraints and anti-patterns
  • Limit palette to 2–4 colors beyond neutrals; assign 60/30/10 dominance
  • Use OKLCH for perceptual uniformity when generating scales and tints
  • Always meet WCAG contrast ratios and never rely on color alone for meaning
  • Apply color systematically: semantic states, primary actions, subtle surface tints, and decorative accents

Example use cases

  • Colorize a telemetry dashboard: green for healthy metrics, amber for warnings, coral for errors, blue for info; tint card surfaces for grouping
  • Make CTAs and primary actions stand out using the dominant brand color and a contrasting accent for destructive actions
  • Enhance charts and reports with a small, consistent categorical palette for comparisons and time series
  • Add status badges and progress rings with semantic colors for instant recognition
  • Introduce subtle gradient or tinted sections to separate onboarding steps or marketing hero areas

FAQ

What information do you need to start?

I need target audience, desired use-cases, brand personality/tone, and any existing brand colors or style tokens. Provide screenshots or code references if available.

Do you run any design checks first?

Yes — I will run a frontend-design analysis to capture principles and anti-patterns. I cannot proceed without its output and explicit brand/context answers.