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.
What this skill does
Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. ## MANDATORY PREPARATION Invoke /impeccable — 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 /impeccable teach 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.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.