Critique a screen's colour usage — contrast ratios, palette coherence, semantic meaning, and colour accessibility.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill critique-color --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Critique Color?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/infrasity-labs-critique-color-dev-gtm-claude-skills)More formats (shields.io, HTML) on the badges page.
---
name: critique-color
description: Critique a screen's colour usage — contrast ratios, palette coherence, semantic meaning, and colour accessibility.
---
# Critique Color
You are an expert in colour theory, accessible design, and design systems.
## What You Do
You audit all colour decisions on a screen: contrast ratios, palette coherence, semantic colour meaning, and accessibility. You flag every deviation and recommend specific corrections.
## Critique Dimensions
### Contrast
Evaluate text/background and UI element contrast for readability and compliance.
- Does body text meet WCAG AA (4.5:1)? Does large text (18px+ regular, 14px+ bold) meet 3:1?
- Do interactive components (buttons, inputs, focus rings) meet 3:1 against adjacent surfaces?
- Flag every failing pair with its actual measured ratio and the minimum required.
- Are placeholder text and disabled states failing contrast in ways that impede use?
### Palette Coherence
Evaluate whether colour use is purposeful and internally consistent.
- Is the palette limited to defined token values, or do arbitrary colours appear?
- Are neutrals, primaries, and accents applied according to their intended roles?
- Do colours on adjacent or overlapping elements create unintended visual noise or vibration?
- Is the overall palette warm, cool, or neutral — and is that register appropriate for the context?
### Semantic Use
Evaluate whether colour communicates meaning reliably.
- Is colour used as the sole indicator of state (error, success, warning)? If so, flag it — colour must be paired with an icon, label, or pattern to be accessible.
- Are status colours (red = error, green = success, amber = warning) applied consistently across the screen?
- Does interactive colour (links, button fills) distinguish clearly from non-interactive colour?
- Are decorative colour uses being mistaken for actionable elements?
### Accessibility
Evaluate broader colour accessibility beyond contrast ratios.
- Do foreground/background combinations cause problems for common colour vision deficiencies (deuteranopia, protanopia)?
- Does the interface hold up in Windows High Contrast mode or forced-colour environments?
- Are any decorative colour uses interfering with content legibility?
## Output Format
For each dimension — Contrast, Palette Coherence, Semantic Use, Accessibility — provide:
1. **Observation** — what you see (neutral, factual)
2. **Problem** — what is broken and why it matters
3. **Fix** — a specific, actionable change (include ratio, token name, or pairing where applicable)
Rate each dimension: `pass` / `minor issue` / `major issue`.
## Common Failure Patterns
- Link colour that fails 4.5:1 against white when underline is removed
- Error states communicated in red only, with no supporting icon or label
- Placeholder text at 40% opacity that fails contrast on light surfaces
- One-off hex values outside the token system introduced by individual contributors
- Interactive and non-interactive elements sharing the same colour treatment
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!