What is the typography-audit skill?
Typography-audit is a skill in mblode/agent-skills that checks web typography only. It applies 78 rules in 10 categories to your CSS, HTML and component files, from font loading and sizing to punctuation, spacing and OpenType features, and reports every finding with a rule ID, file and line, and a fix.
Typography-audit is one folder in Matthew Blode's agent-skills repository. Its SKILL.md opens with a count: 78 rules in 10 categories for web typography. Each rule has its own file, with a short reason it matters and an incorrect and a correct example.
The skill is deliberately narrow. It covers font loading, sizing, punctuation, spacing, hierarchy, text layout, OpenType, pairing, brand type and display type. It does not review accessibility, forms or navigation.
How the audit runs
- Scope the work. The agent lists the changed files, or sweeps everything if you ask, and maps signals in the code to categories.
- Run the CRITICAL rules for the categories in scope: font, size and punctuation.
- Run the HIGH rules, which are the spacing ones.
- Work through the remaining categories in descending priority.
- Report each finding, then re-run only the rules that produced findings after fixes.
For a pull request, the skill diffs against the real merge base, committed changes included, and filters to css, scss, html, tsx, jsx and template files. Rule files load by prefix, so a page with no pairing signal never pays for pairing rules.
The 10 rule categories
| Category | Impact | Rules |
|---|---|---|
| Font selection and weights | CRITICAL | 11 |
| Sizing and measure | CRITICAL | 6 |
| Punctuation and special characters | CRITICAL | 12 |
| Spacing and rhythm | HIGH | 8 |
| Hierarchy and scale | MEDIUM-HIGH | 8 |
| Alignment and layout | MEDIUM | 6 |
| OpenType features | MEDIUM | 7 |
| Brand and identity | MEDIUM | 8 |
| Typeface pairing | MEDIUM | 5 |
| Display and headlines | LOW-MEDIUM | 7 |
Who should run it
Best for
- A pre-merge pass on a pull request that touches fonts, headings or copy.
- A full sweep of a site whose type feels off but cannot say why.
- Teams that want findings with an impact tag and a concrete fix, not a loose opinion.
Not for
- A redesign. Proposing new pairings or scales turns a short review into a design project, so the skill routes that to the ui-design Direction mode in the same repo. For readable type choices, see better-typography.
- Accessibility, forms or navigation. Use the ui-design Audit mode, or fixing-accessibility.
- Judging a loaded font from CSS alone. A declaration does not prove which face loaded.
Use it with UiChemy
Run the audit on the code your agent produced and fix the findings first. To bring the result into WordPress, use UiChemy: AI to WordPress imports an AI build, and Figma to WordPress converts a design. Click Get Started on uichemy.com.
How to install Typography Audit Skill: 78 Rules for Web Type
git clone https://github.com/mblode/agent-skills.gitClone the repository
Run
git clone https://github.com/mblode/agent-skills.git. The skill sits in the skills/typography-audit folder.Copy the whole folder
Copy skills/typography-audit, including its rules folder, to wherever your agent loads skills from. The rule files carry the detail, so a copy of SKILL.md alone is not enough.
Optional companions
The skill refers to ui-design for Audit and Direction modes and to ui-verification for rendered checks. Copy those folders from the same repo if you want those handoffs to work.
Trigger an audit
Use a phrase from the skill description: audit typography, fix the fonts, or review my type system. Name the files, or ask for a full sweep.
Check that it loaded
Ask the agent to audit one stylesheet. It should group findings by file, give each an impact tag, a rule ID and a file:line, and mark clean files as pass.
Key features
- 78 scoped rulesRules are grouped under 10 prefixes: font, size, punct, spacing, hierarchy, layout, opentype, brand, pairing and display. Only the prefixes your code gives a signal for are loaded.
- Signal to category mappingA table links code signals to categories. An @font-face block selects font rules, clamp() and max-width select size rules, and line-height or letter-spacing selects spacing rules.
- Priority orderCRITICAL categories run first, so the worst problems surface even if the audit is cut short. Faux bold and broken punctuation outrank a display-type nit.
- Scoped to the diffBy default the audit covers changed files only. For a pull request it uses the diff against the actual base merge base, and a full sweep happens only on request.
- Findings with a fixed shapeEvery finding carries an impact tag, a rule ID, a file:line location, a one line issue and a fix. Files with no issues are listed as pass, and a summary counts findings per impact level.
- Rule impact, not category impactThe report uses each rule's own frontmatter impact. The skill warns that brand-color is HIGH because it holds a contrast floor, and punct-daggers is LOW-MEDIUM despite its category.
- Rendered copy only for punctuationStraight quotes or double hyphens inside code, pre blocks or script string literals are false positives. Punctuation rules apply to rendered copy.
- OpenType checks that respect the fontThe skill does not flag a missing OpenType feature until the loaded font is confirmed to ship it, since browsers silently ignore unsupported feature tags.
- Optional rendered verificationWhen a finding depends on the computed style or the face that loaded, the skill points to the ui-verification skill in the same repo to confirm it.
Frequently asked questions
What is the typography-audit skill?
It is a skill in the mblode/agent-skills repository that audits web typography with 78 rules in 10 categories. The agent scopes the files, runs the rules by priority and reports findings with a rule ID, a file and line, and a fix. It is not a redesign tool.
How do I install the typography-audit skill?
Clone mblode/agent-skills and copy the skills/typography-audit folder, rules included, into the place your agent loads skills from. Then ask for a typography audit, a font fix or a review of your type system and point the agent at your CSS or component files.
Which agents can use the typography-audit skill?
The repository README gives an install command that targets Codex and Claude Code, and its topics list Claude Code. The skill is a plain SKILL.md with a rules folder, so another agent that loads that format may work, but the repo does not list one.
What does the skill check?
Font loading and weights, sizing and measure, punctuation and special characters, spacing and rhythm, hierarchy and scale, alignment and layout, OpenType features, brand type, typeface pairing, and display headlines. Punctuation rules cover rendered copy only, never code samples.
Does typography-audit fix the problems it finds?
Each finding includes a concrete fix, and the workflow re-runs the rules that produced findings after fixes. The skill is built as an audit, not a redesign, so new typefaces and scales are handed to the ui-design Direction mode. For a related sibling, see better-typography.
How is it different from a full UI review?
Typography-audit covers type only. Broad review of accessibility, forms and navigation belongs to the ui-design Audit mode, which the skill says has shallower typography coverage. Pair them, or use core-web-vitals for page speed effects of font loading.
What license does the typography-audit skill use?
The mblode/agent-skills repository is MIT licensed, shown by the README license section and the GitHub license field. Check the repository again before you redistribute the skill folder, rules included, inside another product.