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.
$ npx -y skills add meodai/skill.color-expert --agent claude-code
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.
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:
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.
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.
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.
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:
yt-dlp, summarized, and key concepts extractedmarkitdown by MicrosoftEverything goes into one of three folders and gets indexed.
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
The repo now includes a minimal review loop rather than a heavy benchmarking framework:
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.evals/task-prompts.md to test whether the skill answers realistic color questions at the right level.MAINTENANCE.md when deciding whether something belongs in SKILL.md, references/, or not in the repo at all.ROADMAP.md to track planned color-specific scripts and larger repo improvements.Counted at the last update; run bash scripts/stats.sh to refresh rather than trusting these.
| Count | |
|---|---|
| Markdown reference files | 181 |
| Total words | ~365,000 |
| Source PDFs (local, gitignored) | 14 |
| Online tools catalogued | 71 |
| Distinct video sources | 109 |
The resources I keep returning to when explaining where color theory came from and where it went wrong:
The theory and science I reference when building tools or explaining why things work the way they do:
The practical resources — the tools I've built, use, or recommend:
Palette generation (actual algorithms, not pre-made swatches):
RampenSau, Poline, pro-color-harmonies, dittoTones, FarbVelo, IQ cosine formula, CSS-native generation with color-mix()
Color libraries: Culori (30 spaces, 10 distance metrics), Color.js (CSS spec editors, 154M downloads), @texel/color (5-125x faster), Spectral.js (Kubelka-Munk), RYBitten (26 historical cubes)
Analysis & linting: Color Buddy (38 lint rules), Censor (CAM16UCS, 20+ viz widgets), Color Palette Shader (WebGL2 Voronoi), colorsort-js (perceptual sorting)
Accessibility: APCA/Myndex (the WCAG 3 algorithm), apcach (contrast-first color composition), Bridge-PCA
Naming: color-name-lists (18 systems), color-description (emotional adjectives), Ridgway digitized JSON, colornerd (29,875 manufacturer swatches)
Generative art approaches: Tyler Hobbs (probability-weighted palettes), Harvey Rayner / Fontana (fully generative color), Piter Pasma (tweaked rainbow formula), mattdesl workshop, Book of Shaders, LYGIA shader library
Practical design: Pixel art palette construction, Goethe edge colors as a design hack, Cubehelix, color harmony lecture ("hue-first is a weak standalone heuristic; character-first often works better"), Aladdin color analysis, screen-to-print workflow
These aren't just preferences — they're supported by the research in the collection:
npx skills add meodai/skill.color-expert
Automatically detects your installed agents and places the skill in the correct directory. Works with Claude Code, Codex, Cursor, Copilot, OpenCode, and others.
Clone and symlink into your agent's skills directory:
git clone https://github.com/meodai/skill.color-expert ~/Sites/color-expert
| Agent | Symlink target |
|---|---|
| Claude Code | ~/.claude/skills/color-expert |
| Codex | ~/.codex/skills/color-expert |
| OpenCode | ~/.agents/skills/color-expert |
| Project-level (any) | .agents/skills/color-expert |
ln -s ~/Sites/color-expert ~/.claude/skills/color-expert
npx skills update
Or manually: cd ~/Sites/color-expert && git pull
The skill activates when your agent detects work involving:
skillcolor-expert is a Claude Code plugin with 1 hand-picked skill, indexed on Flowy in the Design category. Install it with the command on its page. It includes skill.color-expert. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it