PluginBench
Skill
Pass
Audit score 90

critique-typography

owl-listener/designer-skills

Audit typography on screens for scale compliance, readability, consistency, and token usage.

What is critique-typography?

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

  • Audit whether the type scale is applied systematically and each step is used for its intended purpose
  • Evaluate readability: minimum sizes, line-height, measure, letter-spacing, and WCAG contrast ratios
  • Check consistency across semantically equivalent elements (card titles, form labels, etc.)
  • Verify that typography values use design tokens instead of hardcoded CSS or raw values
  • Flag scale drift, line-height mismatches, alignment inconsistencies, and over-use of bold weights

How to install critique-typography

npx skills add https://github.com/owl-listener/designer-skills --skill critique-typography
Claude Code
Cursor
Windsurf
Cline

How to use critique-typography

  1. 1.Provide a screenshot or rendered view of the screen to critique
  2. 2.Specify the defined type scale steps (e.g., display, h1–h4, body-lg, body-sm, caption) and any design tokens in use
  3. 3.Request critique on one or more dimensions: Scale Usage, Readability, Consistency, Token Compliance
  4. 4.Review the observations, problems, and specific fixes provided for each dimension
  5. 5.Apply fixes and re-audit to confirm compliance

Use cases

Good for
  • Review a new screen design to ensure typography follows the system and meets accessibility standards
  • Audit an existing product screen for token compliance and readability issues before handoff to engineering
  • Identify orphaned type treatments and inconsistent styling across a component library
  • Validate that body text meets minimum size thresholds and line-length constraints for legibility
  • Check that all font properties (family, size, weight, line-height, letter-spacing) reference tokens
Who it's for
  • Design systems leads and typography specialists
  • Product designers reviewing screens before development
  • QA and design-review teams auditing consistency
  • Engineers implementing design tokens and type systems

critique-typography FAQ

What's the difference between this skill and `typography-scale`?

`critique-typography` audits how a type scale is applied on a specific screen; `typography-scale` is for defining or building the scale itself.

What readability standards does this skill check?

It evaluates WCAG AA contrast ratios (4.5:1 for body, 3:1 for large text), minimum font sizes (16px desktop, 14px mobile), line-height ranges (1.1–1.3 for headings, 1.4–1.6 for body), and measure (45–75 characters for body copy).

Can this skill check my design tokens are correct?

Yes. It verifies that font-family, font-size, font-weight, line-height, and letter-spacing all reference tokens, and flags any hardcoded values with the correct token name to use instead.

What happens if I don't have a defined type scale yet?

Use `typography-scale` (ui-design) to define your scale first. This skill assumes a scale exists and audits compliance against it.

How does this skill rate issues?

Each dimension (Scale, Readability, Consistency, Token Compliance) is rated as `pass`, `minor issue`, or `major issue` based on the severity and impact on usability or system integrity.

Full instructions (SKILL.md)

Source of truth, from owl-listener/designer-skills.


name: critique-typography 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).

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