Colors-LE
Extract every color in a codebase, and say which ones are not in your palette
No editor in the loop? npx -y colors-le-mcp runs the same engine as an MCP server, so an agent can call extract_colors with nothing else installed, and cargo install colors-le puts the same check in a terminal. Every way to install it.
What Colors-LE does
Design systems drift one hard-coded hex at a time. Colors-LE extracts every color from a stylesheet, template or component file — hex, rgb/rgba, hsl/hsla and named colors — then analyses the result: distribution, clusters of near-duplicates, and contrast ratios against WCAG AA and AAA. It reads CSS, SCSS, LESS, Stylus, HTML, JavaScript, TypeScript and SVG.
What people use it for
Palette auditing
Every hex, rgb()/rgba(), hsl()/hsla() and named color across stylesheets, markup and code.
Design-system review
Analyse distribution, cluster similar colors, and spot near-duplicates.
Accessibility checks
Contrast ratios against WCAG AA and AAA via the Validate command.
9 commands in the palette
Open the command palette and type the name. Nothing is bound to a shortcut by default — the editor's keymap is the user's, not ours.
colors-le.extractColorscolors-le.analyzecolors-le.convertcolors-le.filtercolors-le.validatecolors-le.postProcess.dedupecolors-le.postProcess.sortcolors-le.openSettingscolors-le.helpInstall Colors-LE
VS Code
ext install nolindnaidoo.colors-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.colors-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
ZedComing soon
npx -y colors-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and extract_colors appears in its tool list. The one-click listing in Zed's extension registry is a pull request awaiting review. Track the review.
AI agents
npx -y colors-le-mcpRuns Colors-LE's engine as an MCP server, so an agent can call extract_colors with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where it ships
One engine, 6 places to get it. The ids differ by registry — copy the one for the editor you use.
Zed
built from Rust in the tool repocolors-leOpenlisting pending — this links to the open pull request
Where Colors-LE lives
- VS Code Marketplacecolors-le
- Open VSXfor Cursor and VSCodium
- npmcolors-le-mcp
- GitHubsource, issues, changelog
- MCP registryio.github.nolindnaidoo/colors-le
The other 15
Extract every string in a codebase, with its position, so a person can read them
Extract every hardcoded number in a codebase, so a person can check them
Extract every file path in a codebase, and say whether it still points at anything
Extract every URL in a codebase, with its protocol and exact position
Extract every date and timestamp, and the exact instant each one resolves to
Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name
Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside
Extract every IP address, CIDR block and MAC, normalized and classified by scope
Find every regex in a codebase, and report which can be driven into catastrophic backtracking
Check whether a page is scrapeable before the scraper is written, and say when it cannot tell
Find where one dependency is constrained differently across a repository's manifests
Identify the i18n library a project uses, then audit its catalogs by that library's rules
Find hardcoded credentials in a codebase, and never print one into the report
Compare the dotenv files in a tree, and say which keys are missing from which
Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts