本文へ移動
cccskills
無料GitHub で公開

critique-color

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

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

Format CVs for academic positions with publications, grants, and teaching

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

Create accessibility testing plans covering assistive technologies and WCAG criteria.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

Infrasity-Labs のスキルをすべて見る

このスキルの問題を報告する