⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

color-expert

meodai@meodai⭐ 656 stars· last commit 25d ago· 0 open issues

Use when working with color naming, color theory, color spaces, color definitions, or any task involving color knowledge - palettes, ramps, gradients, conversions, accessibility, perceptual matching, pigment mixing, print-vs-screen color, CSS color syntax, or historical color terminology. Use this skill whenever the user is choosing, comparing, generating, naming, converting, or explaining colors, even if they do not explicitly ask for "color theory.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐ 656 on GitHubGitHub ↗

Popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

color-expert

An agent skill that turns your coding agent into a color science expert. Built from resources I keep looking up, returning to, and sharing with others.

What this is

This started as a simple skill file with some color theory notes. Over time it grew into a comprehensive knowledge base as I kept pasting videos, articles, tools, and papers that I find myself referencing again and again — both for my own work building color tools and for explaining color concepts to others.

The skill has three layers:

  1. SKILL.md — The "greatest hits" that your agent loads immediately. Key facts, corrections, tool recommendations, and guidelines that answer most color questions without needing to dig deeper.

  2. references/INDEX.md — A compact map, one line per reference file, meant to be read whole when the agent needs to find the right file. Full summaries and source links live in per-directory indexes (references/*/INDEX.md) that are only opened when the one-liner is too terse to choose.

  3. references/ — Deep reference material: full video transcripts, article summaries, library documentation, scraped websites, and research notes.

There is also a lightweight evals/ folder for realistic trigger and task prompts so the skill can be reviewed against actual usage instead of only edited by intuition. evals/TRIGGERING.md states the rule those trigger cases encode, so the boundary is arguable in writing rather than per-case.

How it was built

The collection process is simple: when I come across a color resource worth keeping — a YouTube video, a GitHub repo, a research paper, an article — I paste the URL and the skill's workflow captures it:

  • Videos get transcribed via yt-dlp, summarized, and key concepts extracted
  • PDFs and documents get converted to markdown via markitdown by Microsoft
  • GitHub repos get their README/docs fetched and documented
  • Articles get their content extracted and saved
  • Books mentioned in videos get searched on Archive.org; freely available PDFs get downloaded
  • Websites (like huevaluechroma.com) get fully scraped chapter by chapter
  • Tools and links mentioned in any resource get collected into the Online Tools table

Everything goes into one of three folders and gets indexed.

Structure

SKILL.md                              # The skill definition (loaded on activation)
CLAUDE.md                             # Claude Code repo instructions
references/
  INDEX.md                            # Compact map: one line per reference file
  PDFS.md                             # Primary-source PDFs (gitignored, archive.org links)
  historical/                         # Pre-digital color science
    INDEX.md                          # Full summaries + sources for this directory
    *.md                              # Ostwald, Helmholtz, Bezold, Ridgway, ISCC-NBS,
                                      # Moses Harris, Amy Sawyer, Lewis/Ladd-Franklin,
                                      # Caravaggio's pigments, Itten critique...
    pdfs/                             # Source books from Archive.org (gitignored, see PDFS.md)
  contemporary/                       # Modern color science & theory
    INDEX.md                          # Full summaries + sources for this directory
    *.md                              # OKLAB articles, Briggs lectures, CSA webinars,
                                      # Pixar Color Science, bird tetrachromacy, OLO,
                                      # Acerola, Juxtopposed, Computerphile, GenColor paper...
    huevaluechroma/                   # Full scrape of David Briggs's site (11 chapters)
    colorandcontrast/                 # colorandcontrast.com extracted content
    pdfs/                             # Research papers (gitignored)
  techniques/                         # Tools, libraries, methods, practical application
    INDEX.md                          # Full summaries + sources for this directory
    ONLINE-TOOLS.md                   # Pickers, generators and analysers, with what each is for
    *.md                              # Spectral.js, Culori, Color.js, RampenSau, Poline,
                                      # RYBitten, PickyPalette, Color Buddy lint rules,
                                      # APCA/Myndex, IQ cosine formula, Cubehelix,
                                      # Tyler Hobbs generative color, Fontana approach,
                                      # pixel art palettes, Book of Shaders, LYGIA,
                                      # paint mixing lecture, color harmony lecture...
evals/
  TRIGGERING.md                       # The rule the trigger cases encode
  trigger-evals.json                  # Realistic should-trigger / should-not-trigger prompts
  task-prompts.md                     # Realistic color tasks for qualitative review
scripts/
  stats.sh                            # Source of every count quoted in this README
MAINTENANCE.md                        # What belongs where, source quality bar, review rubric
ROADMAP.md                            # Planned scripts and future extensions

Reviewing the skill

The repo now includes a minimal review loop rather than a heavy benchmarking framework:

  1. Use evals/trigger-evals.json to sanity-check whether the frontmatter description is likely to trigger in the right situations, and evals/TRIGGERING.md when a case looks arguable.
  2. Use evals/task-prompts.md to test whether the skill answers realistic color questions at the right level.
  3. Use MAINTENANCE.md when deciding whether something belongs in SKILL.md, references/, or not in the repo at all.
  4. Use ROADMAP.md to track planned color-specific scripts and larger repo improvements.

What's in it

By the numbers

Counted at the last update; run bash scripts/stats.sh to refresh rather than trusting these.

Count
Markdown reference files185
Total words~370,000
Source PDFs (local, gitignored)14
Online tools catalogued74
Distinct video sources109

Historical color science

The resources I keep returning to when explaining where color theory came from and where it went wrong:

  • Ostwald (1918–1930) — the 24-hue perceptual circle that dominated the 1930s–40s then disappeared
  • Helmholtz (1856) — foundational physiological optics; last major physicist to use "indigo"
  • Bezold (1874) — killed indigo as a spectral color; renamed it "ultramarine blue"
  • Ridgway (1912) — 1,115 named colors for naturalists; fully digitized as JSON
  • ISCC-NBS (1955) — 319 systematically named color blocks
  • Moses Harris (1769) — the origin of bad RYB color theory (his own wheel needed a 4th pigment)
  • Amy Sawyer (1911) — patented a CMY wheel decades before it was mainstream
  • Elizabeth Lewis (1931) — married trichromatic + opponent process, anticipating CIE Lab/Luv by decades
  • Plus: Caravaggio's copper resinate technique, Itten's seven contrasts (critically reviewed), the evolution of "magenta" as a color name, Frank Reilly's controlled palette

Contemporary color science

The theory and science I reference when building tools or explaining why things work the way they do:

  • Bjorn Ottosson's OKLAB articles — all four foundational posts (OKLAB, color picker spaces, gamut clipping, "how software gets color wrong")
  • David Briggs's huevaluechroma.com — fully scraped, 11 chapters + glossary
  • colorandcontrast.com — UI-focused color science reference, extracted from SPA bundle
  • Color Nerd (Peter Donahue) — 20+ video transcripts covering mixing paths, spectral perception, warm/cool, chroma vs saturation, bird vision, OLO
  • **Colour Society of Aust

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • SKILL.md7.9 KBupstream ↗
    ---
    name: color-expert
    description: Use when working with color naming, color theory, color spaces, color definitions, or any task involving color knowledge - palettes, ramps, gradients, conversions, accessibility, perceptual matching, pigment mixing, print-vs-screen color, CSS color syntax, or historical color terminology. Use this skill whenever the user is choosing, comparing, generating, naming, converting, or explaining colors, even if they do not explicitly ask for "color theory."
    ---
    
    # Color Expert
    
    A comprehensive knowledge base for color-related work. See `references/INDEX.md` for a one-line-per-file map of 180+ reference files; this skill file contains the essential knowledge to answer most questions directly.
    
    ## How to Use This Skill
    
    Match the response to the user's explicit request and clearly implied constraints from context. Five common modes:
    
    **Concrete design or art project** — "help me pick colors for my logo / poster / illustration / app." Ask about medium (print, screen, paint, mixed), brand or mood, audience, accessibility needs, and any existing colors to harmonize with. Then propose. Don't lecture about CIE 1931 or OKLCH internals unless asked. Recommend specific tools and palettes that fit the constraints, not generic theory.
    
    **Design system, ramps, or theme tokens** — "build me a 9-step accent scale", "palette for light + dark mode", "Tailwind/Radix-style ramps", "what's the right gray ramp for our brand?" Prioritize in this order:
    
    - Use OKLCH to build perceptually uniform scales (consistent lightness across hues, no muddy mid-tones).
    - Build a token graph: reference tokens (palette) → semantic tokens (surface, on-surface, accent, success, warning, danger) → component usage; see *Implementation Guidance* below.
    - Verify every text/background pair against APCA or WCAG in both light and dark.
    - Suggest tools only as needed: Huetone (LCH/OKLCH builder), Leonardo (contrast-ratio-driven ramps + adaptive theming, Adobe), Components.ai Color Scale (parametric), dittoTones (extract perceptual DNA from Tailwind/Radix), Color Buddy (lint). For dataviz sequential/diverging ramps specifically, CuspHanger (Wijffelaars model in OKLCH, in-gamut by construction) or viscm (the viridis editor: live perceptual-derivative diagnostics + CVD + grayscale while you drag control points).
    
    The test for a sequential ramp is **flat perceptual derivative** — plot the perceptual step size between consecutive samples; it should be a horizontal line, in color *and* in grayscale. Bumps are regions where the ramp exaggerates change that isn't in the data (this is jet's core failure, not its ugliness).
    
    **Generative art / creative coding** — "color for my fxhash piece", "palette for thousands of generated strokes", "paint-like mixing in p5.js / WebGL." Different from building a palette generator: the code *is* the artwork, and the user wants to understand the *techniques*, not copy a named artist's style. Help them compose their own system. Useful techniques to teach and combine:
    
    - **Tight constraint, then variation** — pick 3–7 hues in a narrow lightness or chroma band; variety comes from density and interaction, not palette size.
    - **Weighted / probability-based hue selection** — assign each color a weight so some appear often, others rarely; this is what makes a generative output feel curated instead of random.
    - **Narrow-band hue jitter** — small random hue offset within a fixed envelope keeps strokes feeling related but not identical.
    - **Lightness variation at fixed chroma** — depth and atmosphere without losing palette identity (use OKLCH).
    - **Spectral / K-M mixing** (Spectral.js, Mixbox) for paint-like overlap and secondaries; RGB averaging gives muddy, dull results in the same situation.
    - **IQ cosine palette** — `a + b·cos(2π(c·t + d))` for cyclic / periodic schemes from 12 floats.
    - **Anchor-based interpolation** (Poline) — set 2–3 anchors in OKLCH, get an interpolated ramp.
    - **Hue / lightness / chroma trajectories with easing** (RampenSau) — walk each axis along an easing function, color-space-agnostic; great when you want a deterministic ramp shape rather than random anchors.
    - **Harmony-aware generation with muddy-zone avoidance** (pro-color-harmonies) — adaptive OKLCH harmony with 4 styles × 4 modifiers; skips perceptually muddy regions automatically.
    - **Generation in historical / non-digital color spaces** (RYBitten) — work in RYB or one of 26 historical color cubes when you want a painterly feel that strict sRGB/OKLCH can't reach.
    - **Palette cycling / indexed color** — store an index buffer and a small palette, then animate the palette (rotate, ease, or drive from an OKLCH trajectory) instead of the pixels; motion for one lookup per pixel. Works only if each cycle range is a perceptually even closed ramp. See `references/techniques/color-cycling-indexed-palette-animation.md`.
    - **Scene-light sampling** (ray-color) — raytrace a sphere in a room with up to 3 colored lights and sample colors off its surface; coherence comes from shared illumination physics (like an object photographed under one light) rather than color-space geometry.
    - **Sun-lit ramps** (Lightfield, tol.is) — same idea aimed at design tokens: OKLCH pigments on a flat-shaded city under a Planckian-locus sun; each 50–950 ramp is a sweep of surface orientations, re-spaced in L. Adds relative chroma, cusp pull, and a hue-profiled Bezold–Brücke/Abney warm shift (toward red going dark, toward yellow going light; cool hues untouched).
    
    See `references/techniques/` for tyler-hobbs, fontana, mattdesl, iq-cosine, spectraljs, poline, rampensau, pro-color-harmonies, rybitten, ray-color, lightfield (these document the techniques, not styles to imitate).
    
    **General color question** — "what is OKLCH?", "why does my gradient go gray in the middle?", "is APCA better than WCAG?" Answer directly from this skill file or `references/INDEX.md`, and cite the relevant reference. Skip tooling unless they're asking how to do something. **Approachable and accurate usually conflict** — the tidy model (RYB primaries, 12-hue wheel, "red is opposite green") is easy precisely because it summarizes beliefs rather than measurements. Give the tidy version *and* say where it breaks; don't let "easy" quietly become "wrong." (Color Nerd, `references/contemporary/color-theory-dogma-problem.md`)
    
    **Building a generator, tool, or palette algorithm** — "I want to make a palette generator", "how do I generate accessible color scales?", "give me an OKLCH ramp function." Default to recommending an existing library before hand-rolling (Culori, Poline, RampenSau, Spectral.js — see Recommended Tools). Show working code in the user's stack, picking the color space per the table above.
    
    When the user asks to generate or compare palettes, **showcase multiple approaches with their trade-offs before narrowing to one** — anchor-based (Poline), hue-cycling (RampenSau), cosine (IQ formula), harmony-based (pro-color-harmonies), scene-lit (ray-color), and extraction-from-system (dittoTones) suit different problems. Don't be shy about presenting options.
    
    Never recommend coolors.co — it doesn't generate palettes, it picks from a hardcoded list of 7,821 pre-made ones (see Recommended Tools).
    
    ## Color Spaces — What to Use When
    
    | Task                            | Use                                    | Why                                                                       |
    | ------------------------------- | -------------------------------------- | ------------------------------------------------------------------------- |
    | Perceptual color manipulation   | **OKLCH**                              | Best uniformity for lightness, chroma, hue. Fixes CIELAB's blue problem.  |
    | CSS gradients & palettes        | **OKLCH** or `color-mix(in oklab)`     | No mid-gradient darkening like RGB/HSL                                    |
    | Gamut-aware color picking       | **OKHSL / OKHSV**                      | Ottosson's picker spac
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/meodai-skill-color-expert.md

// REPO STATS

656 stars
0 open issues
Last commit: 25d ago