agentsclimarketplace
Sign in

Critique color

Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/critique-color

Critique a screen's colour usage — contrast ratios, palette coherence, semantic meaning, and colour accessibility.From its SKILL.md

Install
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill critique-color

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.0 KB, 582 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most review quality skills give in 582 tokens

Counted across 1,273 of the 2,403 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 63 of 1273, across 62 files
  • Provide a recommended answer for each questionin 47 of 1273, across 45 files
  • Rank findings by severityin 44 of 1273
  • Use parameterized queries for database accessin 38 of 1273, across 20 files
  • Validate all user input with schemasin 33 of 1273, across 15 files
  • Store secrets in environment variablesin 32 of 1273, across 14 files
  • Explore the codebase to answer questionsin 31 of 1273, across 29 files
  • Store tokens in httpOnly cookiesin 30 of 1273, across 12 files
  • Implement rate limiting on API endpointsin 30 of 1273, across 12 files
  • Sanitize user-provided HTMLin 29 of 1273, across 11 files
  • Return generic error messages to usersin 28 of 1273, across 10 files
  • Cite file and line for every findingin 28 of 1273, across 25 files

Said here and by no other author read

  • Rate each dimension as pass, minor issue, or major issue
  • Evaluate contrast ratios for text and UI elements
  • Check palette consistency against defined token values
  • Verify semantic meaning of colours
  • Assess accessibility for colour vision deficiencies
  • Flag every failing contrast pair

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.