color-system
Installation
SKILL.md
color_goal = $ARGUMENTS
Design color as a living system. Judgment sets intent, relationships, and direction; deterministic helpers handle the parts where math beats intuition.
For methods, review loops, and helper-script patterns: !references/color-method.md
Calibration
- Color is relational. Judge any color by what it sits on, sits next to, carries as text, and represents as state — never in isolation. A palette that reads well as a list of values but fails on buttons, badges, forms, charts, tables, or dark mode is unfinished.
- Fit beats theory. Infer the desired feeling, trust, energy, and emphasis from the actual task. A theoretically elegant palette that feels wrong in context is wrong. Don't force the work into canned categories or "what palette type is this?".
- Reason in lightness, chroma, hue. Lightness → hierarchy & legibility. Chroma → intensity & restraint. Hue → temperature, meaning, emotional direction. State changes usually move by lightness and chroma first, dramatic hue jumps last.
- Passing contrast is necessary, not sufficient. A system can pass WCAG and still feel generic, noisy, flat, or emotionally wrong.
- Differentiate on purpose. Fitting category expectations vs claiming visual territory others avoid is a conscious choice — state which you're making.
- Match depth to stage. Early exploration wants direction and interpretation, not token architecture. Reserve ramps, tokens, and validation for refinement.