Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
A skill your agent uses when building a design token system, creating accessible colour palettes, generating colour ramps programmatically, or migrating a design system to support wide-gamut displays.
Install Color Oklch
$ npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist color-oklch --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/color-oklch .claude/skills/color-oklch && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "color-oklch" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/color-oklch into .claude/skills/color-oklch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "color-oklch", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/color-oklchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist color-oklch --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/color-oklch .agents/skills/color-oklch && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "color-oklch" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/color-oklch into .agents/skills/color-oklch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "color-oklch", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist color-oklch --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/color-oklch .cursor/skills/color-oklch && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "color-oklch" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/color-oklch into .cursor/skills/color-oklch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "color-oklch", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/color-oklch--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist color-oklch --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/color-oklch .gemini/skills/color-oklch && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "color-oklch" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/color-oklch into .gemini/skills/color-oklch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "color-oklch", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist color-oklchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/color-oklch .github/skills/color-oklch && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "color-oklch" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/color-oklch into .github/skills/color-oklch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "color-oklch", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist color-oklch --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/color-oklch .opencode/skills/color-oklch && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "color-oklch" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/color-oklch into .opencode/skills/color-oklch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "color-oklch", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
color-oklch- GitHub stars
- 74k
- Token cost
- ~564 tokens
- SKILL.md length
- 267 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when building a design token system, creating accessible colour palettes, generating colour ramps programmatically, or migrating a design system to support wide-gamut displays.
- Building a design token system
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Creating accessible colour palettes
What it does
Color Oklch is an agent skill from thedaviddias/Front-End-Checklist. Use when building a design token system, creating accessible colour palettes, generating colour ramps programmatically, or migrating a design system to support wide-gamut displays.
Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Frontend & Design, covering Theming and dark mode, Design systems and Design tokens. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Building a design token system
- Creating accessible colour palettes
- Generating colour ramps programmatically
- Migrating a design system to support wide-gamut displays
Example prompts
- “/color-oklch”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Color Oklch loads about 564 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 267 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 267 words, ~564 tokens.
Download SKILL.mdSave it as
.claude/skills/color-oklch/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- color-oklch
- description
- Use when building a design token system, creating accessible colour palettes, generating colour ramps programmatically, or migrating a design system to support wide-gamut displays.
- metadata.category
- css
- metadata.priority
- low
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 20
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/css/color-oklch
Use oklch() and oklab() for perceptually uniform colour palettes
HSL and hex colours are defined in the sRGB colour space, which is not perceptually uniform — a 10 % lightness change looks dramatically different depending on the hue. This makes creating accessible, harmonious palettes by hand extremely difficult. oklch corrects this: adjusting the L channel produces the same perceived brightness change regardless of hue or chroma, making it far easier to build accessible colour ramps, dark-mode palettes, and consistent hover/active states.
Quick Reference
- oklch(L C H) — Lightness, Chroma, Hue — is the most practical perceptually uniform colour space for design systems
- Equal lightness steps in oklch look equal to the human eye; equal steps in hsl do not
- Define your colour palette tokens in oklch custom properties
- Use @media (color-gamut: p3) to serve wide-gamut colours to capable displays
Check
Check whether the CSS colour tokens use oklch() or a perceptually uniform colour space, or whether they use hsl/hex which may produce inconsistent perceived lightness across hues.
Fix
Convert the colour token palette from hsl/hex to oklch, ensuring the lightness (L) axis is consistent across all hues in the same shade step.
Explain
Explain what perceptual uniformity means in colour spaces, why oklch is better than hsl for design systems, and how the L, C, H channels map to human colour perception.
Code Review
Review CSS custom properties for colour tokens. Flag palette definitions in hsl or hex that use hardcoded values without a systematic lightness ramp, especially if they are intended to be interchangeable shade steps.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/css/color-oklch
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/color-oklch of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Color Oklch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Color Oklch this skillthedaviddias/Front-End-Checklist | 74k | — | ~564 | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Scalar Design Systemscalar/scalar | 16k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Material Design 3 UI/UX Guideskydashnet/material-design-3-ui-skill | 138 | — | ~3k | Automated safety check: Pass | MIT | |
| UI Design Systemtry-works/role-model | 117 | — | ~5k | Automated safety check: Pass | MIT | |
| Tailwind V4 Shadcnever-works/ever-works | 162 | 2 repos | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Scalar Design System
scalar/scalar
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library.
Material Design 3 UI/UX Guide
skydashnet/material-design-3-ui-skill
Guides designing, reviewing or implementing interfaces that follow Google's Material Design 3 system: semantic tokens, component states, adaptive layout and accessibility.
UI Design System
try-works/role-model
React UI component systems with TailwindCSS + Radix + shadcn/ui.
Tailwind V4 Shadcn
ever-works/ever-works
Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React.
Qt Figma Token Extraction
TheQtCompanyRnD/agent-skills
Extract design tokens, text styles, and variables from a Figma design system and produce a design-tokens.json plus ready-to-use QML singletons.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Color Oklch
What does Color Oklch do?
A skill your agent uses when building a design token system, creating accessible colour palettes, generating colour ramps programmatically, or migrating a design system to support wide-gamut displays. Color Oklch is an agent skill from thedaviddias/Front-End-Checklist. Use when building a design token system, creating accessible colour palettes, generating colour ramps programmatically, or migrating a design system to support wide-gamut displays.
When should I use Color Oklch?
Color Oklch fits situations like: building a design token system; creating accessible colour palettes; generating colour ramps programmatically; migrating a design system to support wide-gamut displays.
How do I install Color Oklch in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a claude-code`. Or copy the skill folder (skills/color-oklch in thedaviddias/Front-End-Checklist) into .claude/skills/color-oklch in your project. Claude Code loads it when a task matches its description.
How do I install Color Oklch in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a codex`. Or copy the skill folder (skills/color-oklch in thedaviddias/Front-End-Checklist) into .agents/skills/color-oklch in your project. Codex loads it when a task matches its description.
Can I use Color Oklch in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill color-oklch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/color-oklch, .gemini/skills/color-oklch, .github/skills/color-oklch and .opencode/skills/color-oklch in your project.
What does Color Oklch need to run?
SKILL.md names no scripts, command-line tools or credentials: Color Oklch is instructions for the agent only.
Does Color Oklch access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Color Oklch safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Color Oklch use?
Color Oklch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Color Oklch use?
About 564 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Color Oklch?
Skills that share tags, products or a category with Color Oklch: Figma Design System Builder (warpdotdev/warp, 65k stars), Scalar Design System (scalar/scalar, 16k stars), Material Design 3 UI/UX Guide (skydashnet/material-design-3-ui-skill, 138 stars) and UI Design System (try-works/role-model, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Color Oklch?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.