better-colors

Crea y verifica sistemas de color generando paletas, asignando nombres a tokens semánticos, convirtiendo entre formatos y midiendo el contraste.

npx skills add https://github.com/jakubkrehel/skills --skill better-colors

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).

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, component hover, border, solid fill, body text. Do not generate a step no role consumes. Both the Tailwind 50–950 and Radix 1–12 conventions map to those roles (palette-structure.md).

Name primitives by hue, semantics by role

Primitives name a value (--blue-600) and are never applied in a component. Semantic tokens name a job (--color-text-secondary), point at a primitive and are the only tier components reference. That seam is what lets a theme repoint colors without touching components (token-naming.md).

Use a token only in its role

Never borrow a token because its value is right today. A separator used as a text color works until borders get lighter, and then the text goes with them. If a role has no token, add the token.

Hold the hue across the ramp

A ramp holds one hue end to end, peaks in vividness mid-ramp and steps more finely at the light end. Build it with a color library, never by eye (palette-generation.md).

One color, one meaning

Use a color for one purpose across the whole interface, treating anything within 15° of OKLCH hue as the same color (color-usage.md). Never let color be the only carrier of meaning. Pair it with an icon or a label, a requirement better-accessibility owns.

Fill exactly one action per view

When filled color encodes primary emphasis, one primary action gets it and peers stay neutral. Put the color on the background, not the label. A filled button reads as primary across the room; accent-colored text on a neutral button reads as a link.

Keep an established hierarchy that already signals emphasis another way. Several colored backgrounds are fine when they encode distinct states or categories rather than competing as peers.

Measure the rendered pair, then report

Measure a foreground against the background it actually renders on, not the page background. When a pair fails, report the pair, its measured value and the threshold it misses, then leave the colors alone. They are a design decision. Change them only when asked, and remeasure after (contrast.md).

Pick a gradient's interpolation space

The space is a look, not a correctness setting. Default to in oklab, and reach for in oklch when a two-hue gradient goes gray in the middle (color-usage.md).

Before you finish

PatternFix
A hex, rgb( or oklch( literal in a component file where a token existsReuse or add the role token, in the project's notation
One oklch( value in a codebase otherwise written in hexWrite it in the established notation unless a migration is in scope
var(--blue-600) or bg-blue-600 in a component filePoint a semantic token at the primitive and use that
A semantic name containing a hue or a component, as in --color-blue-button or --color-sidebar-grayRename it for its role: --color-accent-solid, --color-bg-surface
--color-primary and --color-text-primary both definedRename the brand token accent
A border or separator token inside color:, or a text token inside background:Add a token for the missing role
hsl( ramp values that differ only in lightnessRebuild with a constant perceived hue, in the project's notation
50–200 stepping as far apart in OKLCH L as mid-ramp steps doTighten the light end to about 0.04–0.05 per step
One chroma or saturation number copied across every hue's rampUse the same proportion of each hue's own maximum
A status hue within 15° of the accent hueMove it at least 15° away, or give the destructive action a distinct treatment
Dark tokens equal to the light ramp in reverse step orderLower the accent's chroma, widen the dark end and remeasure every pair
Color tokens set under both prefers-color-scheme and a .dark classPick one switching mechanism and use it throughout
A contrast fix that changes hue and leaves lightnessChange lightness, the channel contrast responds to
prefers-contrast: more overriding a color for both appearances in one blockGive each appearance its own increased-contrast value
Text on a color with alpha, such as /50, rgba( or color-mix( with transparentMeasure the rendered result, or use a solid token
text-white on a Tailwind 500 fillMeasure and report it; white on most 500 hues and several 600 hues fails 4.5:1
oklch() chroma beyond sRGB with no sRGB value declared before itDeclare the sRGB value first, then the vivid one inside @media (color-gamut: p3)

Reporting

Verification. Without a browser: token values, the gamut of every declared color, both theme blocks present and contrast computed from the declared token pair. With one: the background actually rendered behind the text, including opacity and any image beneath it, measured in both light and dark. Report every check you could not run as Not verified.

A standalone review takes its severity ladder and format from reporting.md.

Más skills de jakubkrehel

better-accessibility
jakubkrehel
Revisa y corrige el comportamiento del teclado y el foco, ARIA, los nombres accesibles, los formularios, los anuncios para lectores de pantalla, el movimiento y el zoom según WCAG 2.2.
developmenttestingcode-review
better-interface
jakubkrehel
Revisa una pantalla, un flujo o una interfaz completa en cuanto a accesibilidad, diseño, redacción, tipografía, color, acabado de la interfaz y movimiento, y devuelve un único informe ordenado por prioridad.
designcode-reviewtesting
better-layout
jakubkrehel
Define la agrupación, la alineación, el orden de lectura, la estructura adaptable y el espacio para el texto traducido, para que el diseño se mantenga al cambiar de tamaño, traducirse o reflejarse.
designdevelopment
better-motion
jakubkrehel
Decide qué debe animarse y lo crea, con valores exactos de duración, aceleración, escala y distancia, y recetas para entradas, salidas, cambios de iconos, animación de diseño compartido y arrastre.
designdevelopment
better-typography
jakubkrehel
Configura y revisa cómo se representa el texto, desde la escala tipográfica y el espaciado hasta las características de las fuentes, el ajuste de línea, el truncamiento y la puntuación.
designdevelopment
better-ui
jakubkrehel
Perfecciona superficies e iconos con valores exactos para el radio de borde, la alineación óptica, las sombras y los estados de los iconos.
designdevelopment
better-writing
jakubkrehel
Redacta y revisa textos de interfaz, desde etiquetas y mensajes de error hasta estados vacíos y confirmaciones, para que reflejen la voz del producto e indiquen a las personas qué hacer a continuación.
documentdesigncommunication
make-interfaces-feel-better
jakubkrehel
We need to translate the given text from English to Spanish. The text is a description of an agent skill. We must preserve the name "make-interfaces-feel-better" but it's not in the text, so we don't include it. We translate only the text inside <text>. No extra labels, no markdown, just the translation. The text: "Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows." Translate to Spanish. Keep technical terms like UI, frontend, animations, etc. as is or use common Spanish equivalents? Usually "UI" is kept, "frontend" is kept, "animations" -> "animaciones", "hover states" ->
developmentdesign