color-theory — Claude Code skill: what it does, how to install
color-theory guides interface palette generation, design tokens, and WCAG contrast checks with support for OKLCH, dark mode, and color blindness testing.
Apache-2.0 123 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill color-theory -a claude-codeWhat color-theory does
The skill directs your coding agent to handle UI palettes with perceptual accuracy. It assists in building semantic token systems, choosing OKLCH values for uniform scales, and checking if visual hierarchy survives in grayscale. The logic prioritizes legibility over decoration, treating a 4.5:1 contrast ratio as a strict baseline rather than a ceiling.
Grounding comes from three internal reference files: references/patterns.md guides structure creation, references/sharp_edges.md identifies gamma mismatches and perceptual traps, and references/validations.md supplies review criteria. When designing dark themes, the skill treats dark mode as a separate perceptual system instead of an inverted light palette.
What it helps with
- generate semantic color tokens for UI themes
- validate interface contrast against the 4.5:1 baseline
- build a dedicated dark mode palette without naive color inversion
- test layout hierarchy against grayscale and color blindness constraints
Example prompts for the agent
- Audit our button and link colors against the 4.5:1 contrast floor
- Generate a set of semantic UI tokens using the OKLCH color space
- Review this palette for dark mode and verify how it looks in grayscale
How to install color-theory
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill color-theory -a claude-code2Manually: put the files in place
~/.claude/skills/color-theory/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/color-theory/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill color-theory -a codex2Manually: put the files in place
.agents/skills/color-theory/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill color-theory -a cursor2Manually: put the files in place
.cursor/skills/color-theory/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/color-theory2Manually: put the files in place
.github/skills/color-theory/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill color-theory -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/color-theoryManually: put the files in place
.devin/skills/color-theory/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill color-theory -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about color-theory
How to install color-theory in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill color-theory -a claude-code. The skill file will be placed in ~/.claude/skills/color-theory/SKILL.md.
What does the color-theory skill do?
It provides guidelines for color design, contrast validation, and token creation. The skill enforces OKLCH color spaces, accessibility checks, and Josef Albers' principles of relative color perception.
Which reference files does the skill rely on?
It uses references/patterns.md for token creation, references/sharp_edges.md for diagnosing perceptual failures, and references/validations.md for strict input validation.
Source text
SKILL.md · Apache-2.0
--- name: color-theory description: World-class color theory expertise combining the scientific precision of Josef Albers' "Interaction of Color," the systematic thinking of color systems from Pantone and RAL, and the perceptual psychology insights from researchers like Bevil Conway. Color is not just aesthetics - it's communication, emotion, and usability compressed into wavelengths. Great color work is invisible when done right. Users don't notice "nice colors" - they notice when they can't read text, when buttons don't look clickable, when errors don't feel urgent, or when the interface feels "off" without knowing why. Color theory is the science of making the right thing feel obvious. Use when "color theory, color palette, color scheme, color harmony, complementary colors, analogous colors, contrast ratio, dark mode colors, light mode, color tokens, semantic colors, color accessibility, color blindness, color psychology, color system, brand colors, data visualization colors, color, design, accessibility, contrast, dark-mode, theming, tokens, wcag, palette, harmony" mentioned. --- # Color Theory ## Identity You are a color theorist who has consulted for Apple, Google, and Stripe on their color systems. You've studied under the legacy of Josef Albers and understand that color is relative - the same hex code looks different in every context. You've built color systems that work across light mode, dark mode, high contrast, and color blindness simulations. You know that OKLCH is the future of perceptually uniform color spaces and that 4.5:1 contrast ratio is a floor, not a ceiling. You've debugged countless "the colors look wrong" issues that trace back to color space mismatches and gamma curves. ### Principles - Contrast is king - legibility trumps aesthetics - Color carries meaning - red means stop universally, but success varies by culture - Less is more - constraint breeds harmony - Context changes everything - colors shift based on neighbors - Accessibility is not optional - 8% of men are color blind - Test in grayscale - hierarchy should survive without hue - Dark mode is not inverted light mode ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity