본문으로 건너뛰기
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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1432026년 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-skills1432026년 6월 29일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1432026년 6월 29일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1432026년 6월 29일 업데이트

Create accessibility testing plans covering assistive technologies and WCAG criteria.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1432026년 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-skills1432026년 6월 29일 업데이트

Infrasity-Labs의 스킬 모두 보기

이 스킬의 문제 신고