← ClaudeAtlas

better-colorslisted

Builds and checks color systems by generating palettes, naming semantic tokens, converting between formats and measuring contrast.
madebykaito/kaito-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill madebykaito/kaito-skills
# Colors This skill builds and audits color systems. It generates ramps, maps their steps to roles and token names, converts notation and measures rendered contrast pairs. Never report a contrast value you did not measure, and never estimate a color you could compute. Notation, a tinted neutral and a gradient's interpolation space are project choices, not findings. A broken role mapping, a failing pair and an out-of-gamut step are findings. Perceived lightness throughout means OKLCH `L`, from `0` to `1`. Whether a pair is required to pass belongs to `better-accessibility`. Surfaces, shadows and icon color belong to `better-ui`. ## Match the project's color system Reuse the project's tokens and notation. A consistent hex system beats hex with `oklch()` scattered through it. For a new system, `oklch()` is the best default, because its numbers behave the way the ramp rules below describe. Everywhere else, a color library produces the same ramp in the project's own notation ([color-formats.md](color-formats.md)). ## A system is ramps, not colors One neutral ramp, one accent ramp and only the status ramps the product actually renders. A `warning` ramp nothing imports is maintenance for zero pixels. A second accent hue earns its place only when two things must be distinguishable at a glance. Otherwise use more steps of the one accent ramp. ## Every step has a job A ramp is not a gradient to pick from by eye. Each step exists because a role needs it: page background, compo