01
It starts by itself
PR touches styles. Runs in GitHub Actions or Claude Code routine.
- ↻ PR touches styles
pull_request paths: **/*.css, **/*.tsx
Color tokens stay used by role.
Install the Better Colors skill and make it a habit: follow https://gethabit.dev/skills/jakubkrehel/better-colors.md
31K installs8K starsMIT licenceSource on GitHub ↗

Better Colors
by jakubkrehel · 31K installs
The skill
The better colors skill builds and audits color systems: ramps, semantic token names, format conversion and measured contrast, reported by severity.
Only when you ask.
The habit
Color tokens stay used by role.
↻ Runs by itselfPR touches styles
When does it start? How does it check its work? What does it remember?
Stops after one pull request per run.
Read the project's tokens and notation and match them.
Flag primitives like var(--blue-600) used directly in components.
Flag tokens used outside their role, such as a border token in color.
Look for hue drift, uneven light steps and copied chroma.
Measure each rendered text pair in light and dark and report failures.
Write one row per root cause by severity and end with Block or Approve.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the Better Colors skill helps.
No. It reports the failing pair and its value. Colors change only when you ask.
No. It keeps your notation and suggests OKLCH only for a new system.
Copy the prompt at the top into your agent. It installs the skill from jakubkrehel/skills and sets up the habit. Or run npx skills add jakubkrehel/skills --skill better-colors.
Yes. It is published under MIT. Habit is free too.
Install the Better Colors skill and make it a habit: follow https://gethabit.dev/skills/jakubkrehel/better-colors.md
All jakubkrehel skills →More design skills →
Works in
Made by jakubkrehel, published under MIT. Habit links to the original and never changes it. Is this your skill?