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.
Best use case
colorize is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using colorize should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/colorize/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How colorize Compares
| Feature / Agent | colorize | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
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 directly to clarify what you cannot infer. **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.
Related Skills
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
shader-dev
Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.
remotion-best-practices
Best practices for Remotion - Video creation in React
prompt-engineering-patterns
Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing production prompt templates.
pptx-generator
Generate, edit, and read PowerPoint presentations. Create from scratch with PptxGenJS (cover, TOC, content, section divider, summary slides), edit existing PPTX via XML workflows, or extract text with markitdown. Triggers: PPT, PPTX, PowerPoint, presentation, slide, deck, slides.
planning-with-files
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
pinchtab
Use this skill when a task needs browser automation through PinchTab: open a website, inspect interactive elements, click through flows, fill out forms, scrape page text, log into sites with a persistent profile, export screenshots or PDFs, manage multiple browser instances, or fall back to the HTTP API when the CLI is unavailable. Prefer this skill for token-efficient browser work driven by stable accessibility refs such as `e5` and `e12`.
opencli
OpenCLI — Make any website or Electron App your CLI. Zero risk, AI-powered, reuse Chrome login.