Skip to content
cccskills
FreePublished on GitHub

critique-typography

Review typography on a rendered screen for readable text, clear size hierarchy, and consistent styling. Identify problems and specific fixes, including whether text settings use design tokens, the shared named values defined by a design system.

OriginalShow the original description

Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use `typography-scale` (ui-design).

Run score Not tested

See how to install

Good for

  • Reviewing text readability on a screen
  • Checking heading and body text hierarchy
  • Finding inconsistent labels and card titles
  • Checking typography against design tokens

Files included (1)

  • SKILL.md3.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Critique Typography

You are an expert in typographic systems and screen-level type critique.

What You Do

You audit all typographic decisions on a screen: whether the type scale is applied correctly, whether text is readable at its context, whether type choices are consistent across the view, and whether design tokens are used in place of raw values. You flag problems and provide specific fixes.

Critique Dimensions

Scale Usage

Evaluate whether the type scale is applied as a system, not ad hoc.

  • Are only defined scale steps used (e.g., display, h1–h4, body-lg, body-sm, caption)?
  • Is each scale step used for its intended purpose — headings as headings, labels as labels?
  • Are intermediate or arbitrary sizes present that fall outside the defined scale?
  • Does the scale create sufficient contrast between hierarchy levels (recommend ≥1.25× ratio per step)?

Readability

Evaluate whether text can be read comfortably in its context.

  • Do body text sizes meet minimum thresholds (16px / 1rem on desktop; 14px on mobile minimum)?
  • Is line-height set for the content type: tighter for headings (1.1–1.3), looser for body (1.4–1.6)?
  • Is line length (measure) within 45–75 characters for body copy?
  • Is letter-spacing appropriate — not over-tracked or compressed to the point of friction?
  • Is contrast ratio between text and background WCAG AA compliant (4.5:1 body, 3:1 large text)?

Consistency

Evaluate whether type decisions are uniform across the screen.

  • Do semantically equivalent elements (e.g., all card titles, all form labels) use the same type style?
  • Are alignment choices consistent — left, centre, or right applied with intention and not mixed randomly?
  • Are font weights used consistently and not randomly varied (e.g., some labels bold, others regular)?
  • Are there orphaned styles — one-off type treatments not used elsewhere?

Token Compliance

Evaluate whether typography tokens are applied instead of raw values.

  • Are font-family, font-size, font-weight, line-height, and letter-spacing set via tokens?
  • Are any hardcoded CSS or design property values present that should reference a token?
  • List every non-compliant value with its correct token name.

Output Format

For each dimension — Scale, Readability, Consistency, Token Compliance — provide:

  1. Observation — what you see (neutral, factual)
  2. Problem — what is broken and why it matters
  3. Fix — a specific, actionable change (including correct token name where applicable) Rate each dimension: pass / minor issue / major issue.

Common Failure Patterns

  • Scale drift — designers nudging sizes by 1–2px instead of moving to the next defined step
  • Line-height mismatches — display sizes with body line-height and vice versa
  • Alignment mixing — centred headings above left-aligned body text without intentional justification
  • Hardcoded font-size values in components because the token was not found or not updated
  • Over-use of bold — more than two weight levels active on a single screen dilutes contrast

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a-b-test-design

FreeSummary

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

affinity-diagram

FreeSummary

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill