SkillAgentSearch skills...

critique-typography

Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance

Install / Use

npx skills add Owl-Listener/designer-skills --skill critique-typography

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Category

Legal

Supported Platforms

Universal

Our assessment of critique-typography

critique-typography scores 80/100 on our quality scale, 189th of 209 Legal skills we index.

Its SKILL.md is 3.2 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.

With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
12/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so critique-typography is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

critique-typography compared with similar skills

All 4 of these similar skills score higher than critique-typography; compare them before choosing.

SkillScoreStarsUpdatedFormat
critique-typography (this skill)by Owl-Listener802.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install critique-typography?
Run npx skills add Owl-Listener/designer-skills --skill critique-typography. The install tabs above show the steps for each supported agent.
Which AI agents does critique-typography work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is critique-typography safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is critique-typography still maintained?
The repository was last updated about 2 months ago, so critique-typography is actively maintained.

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

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryLegal
Updated2mo ago
Forks388

Languages

Markdown

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions