Design

Color Palette Generator - Claude MCP Skill

Create beautiful, accessible color schemes for any project

SEO Guide: Enhance your AI agent with the Color Palette Generator tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to create beautiful, accessible color schemes for any project... Download and configure this skill to unlock new capabilities for your AI workflow.

🌟1 stars • 4 forks
šŸ“„0 downloads

Documentation

SKILL.md
# Color Palette Generator

An expert color theorist that creates harmonious, accessible color palettes for any project. This skill combines color theory principles, accessibility standards (WCAG), and modern design trends to generate cohesive color schemes that work across digital and print media.

Whether you need a vibrant brand identity, a calming UI palette, or a bold marketing scheme, this skill provides scientifically-backed color combinations with detailed usage guidelines, contrast ratios, and implementation code.

## Core Workflows

### Workflow 1: Brand Palette Creation
1. Gather requirements:
   - Brand personality (professional, playful, bold, minimal, etc.)
   - Industry context
   - Target audience
   - Desired emotional response
2. Generate primary color options (3-5 choices)
3. Build complementary palette:
   - Primary: Main brand color
   - Secondary: Supporting accent
   - Neutral: Grays/backgrounds
   - Semantic: Success, warning, error, info
4. Validate accessibility (WCAG AA/AAA compliance)
5. Provide usage guidelines and code

### Workflow 2: UI/UX Palette
1. Define interface requirements:
   - Light/dark mode support
   - Number of states needed
   - Content type (data-heavy, content-focused, etc.)
2. Create systematic color scale:
   - Base color with 9-11 tints/shades
   - Semantic colors with matching scales
   - Neutral scale for backgrounds/text
3. Map colors to UI elements:
   - Backgrounds, surfaces, overlays
   - Text hierarchy
   - Interactive states (hover, active, disabled)
   - Borders and dividers
4. Generate Tailwind/CSS variables
5. Create usage documentation

### Workflow 3: Palette from Inspiration
1. Accept input:
   - Image/photo reference
   - Brand logo
   - Competitor site
   - Color hex codes
2. Extract dominant colors using color theory
3. Refine and harmonize:
   - Apply color harmony rules (complementary, triadic, analogous)
   - Adjust saturation/lightness for consistency
   - Ensure sufficient contrast
4. Build complete palette with variations
5. Provide comparison with original

### Workflow 4: Accessibility Audit
1. Receive existing color palette
2. Test all color combinations:
   - Text on backgrounds
   - Button states
   - Interactive elements
3. Calculate contrast ratios (WCAG 2.1)
4. Identify failures and provide fixes:
   - Suggest darker/lighter alternatives
   - Show minimum adjustments needed
5. Generate accessibility report

## Quick Reference

| Action | Command/Trigger |
|--------|-----------------|
| Create brand palette | "Generate a [mood] color palette for [industry]" |
| UI color system | "Create a UI palette for [project type]" |
| Extract from image | "Build palette from this [image/logo]" |
| Check accessibility | "Audit these colors for WCAG compliance" |
| Expand single color | "Create a full palette from #HEX" |
| Export formats | "Give me Tailwind/CSS/Figma variables" |

## Color Harmony Systems

**Monochromatic**: Single hue with varying lightness/saturation
- Use for: Minimal, sophisticated designs
- Best for: Photography sites, portfolios

**Analogous**: Adjacent colors on color wheel (30° apart)
- Use for: Harmonious, natural feel
- Best for: Wellness, nature, eco brands

**Complementary**: Opposite colors on wheel (180° apart)
- Use for: High contrast, energetic
- Best for: Sports, entertainment, retail

**Triadic**: Three colors equally spaced (120° apart)
- Use for: Balanced, vibrant
- Best for: Creative, playful brands

**Split-Complementary**: Base + two adjacent to complement
- Use for: Softer than complementary
- Best for: Professional services, SaaS

**Tetradic**: Four colors in two complementary pairs
- Use for: Rich, complex palettes
- Best for: Content-heavy, editorial

## Best Practices

- **Start with purpose**: Understand the emotional response and brand personality before choosing colors
- **Mind the ratios**: Use 60-30-10 rule (60% primary, 30% secondary, 10% accent)
- **Accessibility first**: Always check WCAG contrast ratios before finalizing
- **Test in context**: Colors look different on screens vs. print, light vs. dark backgrounds
- **Provide variations**: Include tints, shades, and tones for flexibility
- **Consider color blindness**: Test with simulators, ensure critical info isn't color-only
- **Document usage**: Specify which colors for what purpose (buttons, text, backgrounds)
- **Think systems**: Create scalable palettes that grow with the product
- **Cultural awareness**: Colors have different meanings in different cultures
- **Neutral foundation**: Every palette needs a solid gray scale
- **Semantic clarity**: Success, warning, error, info should be immediately recognizable
- **Dark mode ready**: Ensure colors work in both light and dark themes

## Deliverables Format

```
PALETTE NAME
Mood: [Adjectives describing the feel]

PRIMARY COLORS
Main Brand: #HEX - [Name] - RGB(r,g,b) - HSL(h,s,l)
  Usage: Primary buttons, headers, brand moments
  Accessible on: White, Light Gray

Secondary: #HEX - [Name]
  Usage: Accents, highlights, links
  Accessible on: White, Dark Gray

NEUTRAL SCALE
Gray-900: #HEX (Darkest - primary text)
Gray-800: #HEX (Secondary text)
...
Gray-100: #HEX (Lightest - subtle backgrounds)

SEMANTIC COLORS
Success: #HEX (Green family)
Warning: #HEX (Yellow/Orange family)
Error: #HEX (Red family)
Info: #HEX (Blue family)

CONTRAST RATIOS
āœ“ Primary on White: 4.8:1 (AA compliant)
āœ“ Secondary on Light Gray: 7.2:1 (AAA compliant)
āœ— Warning on White: 2.1:1 (FAIL - suggest #HEX instead)

CODE EXPORT
[Tailwind config / CSS variables / Figma styles]

USAGE GUIDELINES
- When to use each color
- Do's and don'ts
- Common combinations
```

## Tools Integration

- Use **Midjourney** for generating color mood boards
- Use **WebSearch** to research industry color trends
- Use **Firecrawl** to analyze competitor color schemes
- Use **Playwright** to test colors in live browser context

## Common Requests

**Startup/Tech**: Blues, grays, vibrant accents
**Finance**: Navy, gold, conservative palette
**Healthcare**: Blues, greens, calming tones
**Food/Restaurant**: Reds, oranges, warm palette
**Eco/Sustainability**: Greens, earth tones, natural
**Luxury**: Black, gold, deep jewel tones
**Children/Education**: Primary colors, bright, playful
**Creative/Agency**: Bold, unconventional, statement colors

Signals

Avg rating⭐ 0.0
Reviews0
Favorites0

Information

Repository
eddiebe147/claude-settings
Author
eddiebe147
Last Sync
2/4/2026
Repo Updated
2/4/2026
Created
1/13/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.

⭐ 23280

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.

⭐ 23280

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

⭐ 14843

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

⭐ 13158

Related Guides