colorize

Add strategic color to monochromatic UI components with WCAG-compliant palettes.

Updated Jan 22, 2025
One-click install
npx skills add https://github.com/SL-A-SH/my-portfolio --skill colorize-sl-a-sh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: colorize
Source: https://github.com/SL-A-SH/my-portfolio/tree/main/.claude/skills/colorize
Command: npx skills add https://github.com/SL-A-SH/my-portfolio --skill colorize-sl-a-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many interfaces are visually flat, overly monochromatic, or lack clear visual hierarchy, making it hard for users to scan, understand states, and feel engaged. This Skill helps designers and frontend engineers add purposeful color that communicates meaning, improves hierarchy, and injects personality without creating visual noise.

Core Features & Use Cases

  • Opportunity assessment: Identify where color adds semantic meaning, hierarchy, categorization, wayfinding, or delight.
  • Palette strategy: Recommend a limited palette (2–4 colors plus neutrals), dominant/secondary/accent roles, and application areas.
  • Accessibility and cohesion: Enforce WCAG contrast ratios, avoid color-only cues, and prefer OKLCH for perceptual uniformity.
  • Use Case: Refresh a monochrome dashboard by assigning a dominant brand color to primary CTAs, a secondary color for highlights, and an accent for status badges while ensuring contrast and semantic consistency.

Quick Start

Apply the colorize skill to the main dashboard component by selecting a dominant brand color, adding one secondary color and one accent, and validating all text and UI contrasts against WCAG guidelines.

Frequently Asked Questions about colorize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve visual hierarchy in a monochromatic UI dashboard?

Improve visual hierarchy by introducing strategic color to flat dashboards, assigning a dominant brand color to primary CTAs, a secondary color for highlights, and an accent for status badges to clarify states.

What is the best way to add semantic colors to a flat frontend component library?

Add semantic colors by assessing opportunities for categorization and wayfinding, then recommending a limited palette of 2 to 4 colors plus neutrals to define dominant, secondary, and accent application roles.

Do I need existing brand colors to apply a strategic UI color palette?

You need existing brand colors or must perform a context-gathering step to define a palette, ensuring introduced colors align with semantic states, call-to-action emphasis, and visual separation.

Does this approach enforce WCAG contrast ratios for UI elements?

Yes, this approach enforces WCAG contrast ratios for text and UI elements, avoids color-only cues for accessibility, and prefers the OKLCH color space to maintain perceptual uniformity across the interface.

Why use OKLCH color space for UI design instead of standard RGB?

Use the OKLCH color space for UI design to achieve perceptual uniformity, ensuring color adjustments for visual hierarchy and semantic states appear consistent and predictable to the human eye.

When should I avoid adding more colors to a visually flat interface?

Avoid adding more colors when it creates visual noise; instead, use a limited 2 to 4 color palette plus neutrals to inject personality and communicate meaning without overwhelming the user's scanning process.