color-audit
Skill8 starsChanged 7 months agoMITView on GitHub
Color-only audit that extracts, evaluates, and recommends improvements for the project's color system. Use when the user asks to audit colors, run a color review or color audit, fix their colors, or work on the color palette or color system.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rome-os/rometheir own version, first seen Oct 21, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rome-os/rome★ 894same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- a11y-auditSkill
- component-auditSkill
- design-auditSkill
- design-checklistSkill
- design-compareSkill
- design-scoreSkill
- design-tokensSkill
- flow-auditSkill
- layout-auditSkill
- refactor-planSkill
- style-directionSkill
- theme-builderSkill
- type-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check contrast ratios for all foreground/background pairs with uiux_check_contrast
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/color-audit: Color System Audit
Focused audit of the project's color system.
Flow
- Extract all colors with
uiux_extract_colors - Map color roles (primary, secondary, neutral, semantic, surface, text)
- Check contrast ratios for all foreground/background pairs with
uiux_check_contrast - Evaluate harmony, consistency, coverage, dark mode
- Generate improved color system with
uiux_generate_palette - Output light + dark mode palettes with token values
Output
- Current color inventory (unique colors, near-duplicates, CSS variables)
- Contrast audit (WCAG + APCA for all pairs)
- Harmony analysis
- Semantic role coverage
- Recommended complete color system (CSS vars or Tailwind config)
- Light + dark mode palettes
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.