Skip to the usage guide
Critique Typographyby owl-listener

Critique Typography Skill.

Audit rendered type against readability and the existing type system.

  • Typography
  • Readability
Source Review · critique-typographySKILL.md
Task Audit rendered type against readability and the existing type system. Produces Findings grouped by scale, readability, consistency and token compliance. Before You Start A screen-level critique needs actual output, not only a list of CSS declarations.
Editorial summary · source reviewed 2026-11-02 · not a generated example

01 What It Does

Audit rendered type against readability and the existing type system

Review a screen's type scale, readability, consistency and token compliance, then produce specific findings and corrections.

Source-based workflowNot an execution benchmark

The Working Approach

Critique Typography examines how type is actually used on a rendered screen. It reviews scale usage, reading comfort, consistency and token compliance. A useful finding identifies both what is visible and which existing style or token should govern it, so the team can correct a specific mismatch.

The source includes concrete review dimensions such as line length, line-height, tracking, contrast and semantic role. It also asks whether equivalent elements receive equivalent treatment. This makes it useful after an interface is built, especially when individual adjustments have gradually weakened the original typography system.

Expected Deliverables

  • Findings grouped by scale, readability, consistency and token compliance.
  • An observation, explanation and actionable correction for each issue.
  • A pass, minor-issue or major-issue rating for each reviewed dimension.
See the Example Brief

From Brief to Review

  1. 01
    Read the rendered type system

    Inspect the screen alongside its defined text styles and tokens. Identify headings, labels, body text and captions by their actual role.

  2. 02
    Assess reading conditions

    Review size, line-height, line length, tracking and contrast in context. Treat numeric guidance in the source as review criteria to evaluate against the product's requirements.

  3. 03
    Compare equivalent elements

    Check whether repeated labels, titles and text blocks use consistent weights, alignment and scale steps. Locate one-off styles and arbitrary intermediate values.

  4. 04
    Map findings to corrections

    For each dimension, separate the neutral observation from the problem and proposed fix. Name the appropriate token wherever an existing definition applies.

02 When to Use It

When to Use It

A screen-level critique needs actual output, not only a list of CSS declarations.

A Good Fit

  • Typography driftA built screen has accumulated arbitrary size or weight adjustments.
  • Focused visual critiqueThe layout is settled, but text hierarchy or reading comfort needs attention.

Limits to Check

  • Rendered evidenceA screen-level critique needs actual output, not only a list of CSS declarations.
  • Existing systemInitial scale definition belongs to the separate typography-scale skill.
  • Scoped assessmentA type review is not a complete accessibility certification or full product audit.

Bring These Inputs

  • Rendered screenProvide the interface at the sizes and states that matter.
  • Type definitionsSupply typography tokens and their intended roles.
  • Content contextInclude real text, language and reading conditions.

03 Decisions That Matter

Decisions That Matter

  1. Specific fixes

    Corrections can point to the exact intended style or token.

  2. Comparable dimensions

    The report separates scale problems from readability and consistency.

  3. Visible evidence

    Findings describe what the reviewer can actually observe.

04 Try a Focused Brief

Try a Focused Brief

The example brief below has not been tested. Check the skill’s setup before using it.

Review the Source and Setup

Provide the interface at the sizes and states that matter.

Upstream Source File
https://github.com/owl-listener/designer-skills/blob/9a6930cf84a822eb458624bd11c61aac5bbdf224/visual-critique/skills/critique-typography/SKILL.md

The reference below opens the upstream instructions. Review the repository setup before using them; it is not an installation command.

Start With One Deliverable

Adapt the scope, source material and constraints in this brief before running the skill.

Example Brief
Use critique-typography on the rendered analytics overview at desktop and mobile widths. Compare visible headings, labels, values and body copy with our typography tokens. Review scale usage, line-height, reading measure, contrast and consistency between equivalent elements. For each dimension, give a neutral observation, explain the problem and propose a specific correction with the correct token name where available. Rate the dimension as pass, minor issue or major issue. Keep the current layout direction and distinguish measured properties from judgments that require further inspection.

Inspect the Result

Check the actual output against these observable criteria.

  • Each issue refers to a visible element and relevant type role.
  • Token recommendations use real definitions from the project.
  • Ratings are accompanied by observations and specific corrections.

OpenDesign provides a local design workspace for coding agents. This listing does not mean the skill is bundled or that its external tools, credentials and software dependencies are included.

05 Source and License

Source and License

This page describes the pinned source revision linked below. Upstream behavior and requirements can change.

Source Owner
owl-listener
Skill File
SKILL.md
License
MIT
Reviewed Snapshot
2026-11-02 · 9a6930cf84a8
Editorial Source Summary
Audit rendered type against readability and the existing type system.

Original summary by OpenDesign, based on the linked source. Repository stars are a dated popularity signal, not skill usage or a quality score.

06 Questions Before You Start

Questions Before You Start

Will it define a new typography scale?

The source focuses on reviewing usage and points scale creation to a separate skill.

What format do findings use?

Each dimension receives an observation, problem explanation, actionable fix and severity rating.

Does it examine hardcoded type values?

Yes. Token compliance includes font family, size, weight, line-height and letter-spacing.

OpenDesign

Keep Your Brief and Design Work Together.

Keep your brief, source material and design work together in a local workspace. Check the skill’s own setup before adding it to your workflow.

Upstream Source File
https://github.com/owl-listener/designer-skills/blob/9a6930cf84a822eb458624bd11c61aac5bbdf224/visual-critique/skills/critique-typography/SKILL.md