General
colorize - Claude MCP 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.
SEO Guide: Enhance your AI agent with the colorize tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to add strategic color to features that are too monochromatic or lack visual interest, making interface... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.mdStrategically 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, 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.
Signals
Information
- Repository
- arlenagreer/claude_configuration_docs
- Author
- arlenagreer
- Last Sync
- 5/10/2026
- Repo Updated
- 5/7/2026
- Created
- 4/10/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
cloud
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2 or v3), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP WebSocket connections, stealth browsers, residential proxies, CAPTCHA handling, webhooks, workspaces, skills marketplace, liveUrl streaming, pricing, or integration patterns (chat UI, subagent, adding browser tools to existing agents). Also trigger for questions about n8n/Make/Zapier integration, Playwright/ Puppeteer/Selenium on cloud infrastructure, or 1Password vault integration. Do NOT use this for the open-source Python library (Agent, Browser, Tools config) — use the open-source skill instead.
browser-use
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
agent-builder
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Related Guides
Mastering the Oracle CLI: A Complete Guide to the Claude Skill for Database Professionals
Learn how to use the oracle Claude skill. Complete guide with installation instructions and examples.
Python Django Best Practices: A Comprehensive Guide to the Claude Skill
Learn how to use the python django best practices Claude skill. Complete guide with installation instructions and examples.
Building Full-Stack Applications with Claude: The Node.js MongoDB JWT Express React Skill Guide
Learn how to use the nodejs mongodb jwt express react Claude skill. Complete guide with installation instructions and examples.