Skip to content
Agent Orchestration
Skill

/colorize

Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.

BOOST
From plugin
ccg
5.9k47 skills19 commands
Install
$ npx -y skills add fengshao1227/ccg-workflow --skill colorize --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/colorize

Context preview

The summary Claude sees to decide when to auto-load this skill.

Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.

SKILL.md

colorize.SKILL.md
name: colorize
description: "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette."
argument-hint: "[target]"
user-invocable: false

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

MANDATORY PREPARATION

Invoke /frontend-design — 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, Ask the user using AskUserQuestion.

**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
Read more
Ships withccg

多模型协作工作流引擎 — /ccg:go 一个命令,AI 自动分析意图、选择策略、编排 Codex + Gemini + Claude 协作执行

Get the whole plugin

Other skills on ccg.

verify-change
Skill

verify-change

变更校验关卡。分析代码变更,检测文档同步状态,评估变更影响范围。当用户提到变更检查、文档同步、代码审查、提交前检查、diff分析时使用。在设计级变更、重构完成时自动触发。

verify-module
Skill

verify-module

模块完整性校验关卡。扫描目录结构、检测缺失文档、验证代码与文档同步。当用户提到模块校验、文档检查、结构完整性、README检查、DESIGN检查时使用。在新建模块完成时自动触发。

verify-quality
Skill

verify-quality

代码质量校验关卡。检测复杂度、重复代码、命名规范、函数长度等质量指标。当用户提到代码质量、复杂度检查、代码异味、重构建议、lint检查、代码规范时使用。在复杂模块、重构完成时自动触发。

verify-security
Skill

verify-security

安全校验关卡。自动扫描代码安全漏洞,检测危险模式,确保安全决策有文档记录。当用户提到安全扫描、漏洞检测、安全审计、代码安全、OWASP、注入检测、敏感信息泄露时使用。在新建模块、安全相关变…