# typography

Adopt this skill: https://proskills.md/skills/other/danium-practicaltypography-skills-typography

Page: https://proskills.md/skills/other/danium-practicaltypography-skills-typography
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: skills/typography/SKILL.md
size: 6649
sha: ada3f925306fb80dd1118bdf7e0244b1e86bf5fa
upstream: https://github.com/danium/practicaltypography/blob/main/skills/typography/SKILL.md

````text
---
name: typography
description: Use when styling or reviewing text in any medium; choosing fonts, size, spacing, measure, headings, emphasis, punctuation, or numeric typography; auditing websites, documents, slides, email, resumes, tables, or PDFs; or resolving a user's visual preference against typographic, accessibility, language, and delivery constraints
---

# Typography

Good typography reinforces the meaning of the text and conserves the reader's attention. Start with body text, but never apply body-text rules to every role. Treat Practical Typography as a benchmark, not a compliance standard. Rule IDs point to [provenance.md](provenance.md), which distinguishes source guidance (`PT`), project choices (`DEVIATION`), and current external requirements (`CURRENT`).

## Load only what the task needs `[ROUTE-001]`

- Character substitutions, punctuation, whitespace, emphasis, or literal text: [composition.md](composition.md)
- Paragraphs, headings, lists, quotations, tables, styles, pagination, columns, or grids: [layout.md](layout.md)
- Font selection, pairing, glyphs, features, or licensing: [fonts.md](fonts.md)
- Websites, responsive measure, actual font use, fallbacks, or accessibility: [web.md](web.md)
- Print, slides, email, resumes, tables of numbers, or PDF delivery: [media.md](media.md)
- Non-English, non-Latin, bidirectional, or mixed-script text: [international.md](international.md)
- Authority, scope, freshness, and evaluation coverage for a rule: [provenance.md](provenance.md)

Do not load every reference by default. A PDF containing Arabic code examples, for example, needs `media.md`, `international.md`, and the literal-text section of `composition.md`; a simple English print paragraph does not need `web.md`.

## Precedence

Apply this order whenever recommendations conflict `[CORE-002]`:

1. content correctness and semantics;
2. accessibility, language conventions, and legal or license constraints;
3. user intent and delivery medium;
4. Practical Typography benchmarks;
5. project presets and optional taste.

Preserve the user's requested aesthetic as far as higher-priority constraints allow. If it departs from a benchmark, label the departure once and give the benchmark alternative without repeatedly arguing the point.

## Gated audit

### 1. Classify context `[AUDIT-001]`

Identify the medium and delivery format, reading environment, intended audience, language and script, user intent, and the roles present: running prose, display heading, navigation, caption, table, code, data, and so on. State a material assumption if it cannot be verified.

### 2. Protect literal and semantic regions `[AUDIT-002]`

Before changing characters, classify spans as prose, code, command, URL, email address, identifier, measurement, legal reference, or data. Transform eligible prose only. Preserve unknown or mixed spans and report uncertainty instead of silently normalizing them. See [composition.md](composition.md).

### 3. Inspect the strongest available evidence `[AUDIT-003]`

Distinguish four levels:

1. authored source or declared styles;
2. computed or application formatting, including the font actually selected;
3. rendered pages, lines, and glyphs;
4. final delivery artifact, such as an exported PDF or printed page.

Use the highest level available and name what was not verified. Never present a source-only inference as a rendered fact.

### 4. Apply constraints `[CORE-002]`

Check semantics, accessibility, language/script behavior, font capability, licensing, and delivery reliability before aesthetic benchmarks. For web work, use [web.md](web.md); for unfamiliar languages or scripts, use [international.md](international.md).

### 5. Apply benchmarks in impact order `[AUDIT-004]`

1. **Body text:** font, size, line spacing, and rendered measure. For English-language running prose, Practical Typography's starting ranges are 15–25 px on the web, 10–12 pt in print, 120–145% line spacing, and about 45–90 actual characters per line `[TYPE-001]`. CSS `ch` is only a setup heuristic because it measures the zero glyph, not average characters; verify representative rendered lines or use the two-to-three-lowercase-alphabets test.
2. **Alignment and paragraphs:** use either first-line indents or paragraph space, not both; do not center running prose; justify only when language-aware line breaking and spacing produce an acceptable result `[TYPE-002] [TYPE-003]`.
3. **Headings:** keep hierarchy restrained, use the smallest visible distinction that works, avoid underlining and untracked caps, make space above exceed space below, and keep headings with what follows `[TYPE-004]`.
4. **Emphasis:** prefer one signal, keep emphasis shorter than a sentence when practical, do not underline non-links, and use genuine small caps with appropriate tracking `[TYPE-005]`.
5. **Composition:** inspect eligible prose for quotes, apostrophes, dashes, ellipses, symbols, ordinals, delimiters, and whitespace without altering literal content `[COMP-001..007]`.
6. **Supporting elements:** apply role-specific guidance for quotations, lists, code, tables, captions, navigation, callouts, slides, and other media. Do not invent exact ratios where visual calibration is the actual test.

### 6. Prioritize and report `[AUDIT-005]`

Report each actionable finding as:

```text
[MAJOR|MINOR] element: observed problem -> correction (value or edit; evidence level)
```

`MAJOR` means the defect materially harms reading, meaning, accessibility, language behavior, or delivery. `MINOR` means refinement whose absence does not materially block reading. Severity is contextual, not a fixed lookup table.

End every audit with:

- corrected values, code, or an edit list;
- the evidence level reached and any verification still needed;
- the three fixes expected to make the greatest improvement.

## Optional presets `[PRESET-001]`

These are project-authored starting points, not Butterick rules. Calibrate them against the actual font, content, viewport, and medium.

| Preset | Starting point | Intended feel |
|---|---|---|
| Bookish | 17–18 px, 1.3–1.4 leading, rendered lines near the middle of the source range, serif, first-line indents | dense, print-influenced |
| Airy screen | 19–21 px, 1.5–1.6 leading, narrower rendered measure, paragraph space | deliberately looser than the PT leading range |
| Compact docs | 15–17 px, 1.35–1.45 leading, wider but verified measure, modest paragraph space | information-dense documentation |

Use the smallest visible adjustment, render alternatives when possible, and judge the result in its delivery context `[CORE-001]`.
````

## File: skills/typography/composition.md
size: 4913
sha: 64b21eefb97473cf25232b1fc3ced9af067ec7e5
upstream: https://github.com/danium/practicaltypography/blob/main/skills/typography/composition.md

```text
# Composition and safe character handling

Load this reference for punctuation, spaces, emphasis, or any character transformation. These rules are validated primarily for English prose in the Latin script. Route other language or script work through [international.md](international.md).

## Classify before transforming `[AUDIT-002]`

Divide text into prose, code, command, URL, email address, identifier, measurement, legal reference, and data. Only transform prose with clear intent. Preserve source spelling and characters in unknown or mixed regions.

Never normalize inside code spans or blocks, shell commands, markup syntax, filenames, paths, URLs, email addresses, IDs, serialized data, or quoted strings whose exact bytes matter. Do not turn `!=`, `=>`, `--flag`, straight programming quotes, or backticks into typographic glyphs. Disable programming ligatures and character substitutions in reader-facing code when they obscure the typed characters `[FONT-004]`.

## Quotes and apostrophes `[COMP-001]`

- Use language-appropriate curly quotation marks and apostrophes in eligible prose.
- Apostrophes point down in contractions and omissions: `don't`, `’70s`, and `rock ’n’ roll` after conversion.
- Preserve straight marks used for feet and inches, straight characters required by code or data, and unfamiliar quotation conventions.
- A leading apostrophe, single closing quote, and prime mark are distinct characters; infer from meaning, not adjacency alone.

## Hyphens and dashes `[COMP-002]`

- Use an em dash for a prose break where the house style calls for it. Butterick sets it closed; another house style may space it consistently.
- Use an en dash for numeric ranges and paired names when appropriate, but write `from 1880 to 1912`, not `from 1880–1912`.
- Keep hyphens in compounds and phrasal adjectives where grammar requires them. Do not replace syntax hyphens or minus signs.

## Ellipses `[COMP-003]`

Use the ellipsis character in eligible prose and keep the adjacent spacing consistent with the house style. When an ellipsis separates words, use nonbreaking spaces where needed to keep the three-part construction together. Preserve three literal periods in code, filenames, commands, data, and APIs.

## Symbols, measurements, and ordinals `[COMP-004]`

- Use ©, ™, and ® only when the author intended those symbols. Do not convert `(c)`, `(r)`, or `(tm)` mechanically; `Section 12(c)` is a legal reference, not a copyright mark.
- Keep the mark attached to its owner and use a nonbreaking space in constructions such as `© 2026` when line breaking requires it.
- Distinguish the multiplication sign from the letter `x`, and a mathematical minus from a hyphen, only when semantics are clear.
- Preserve straight foot and inch marks when they encode measurement, or replace them with prime and double-prime characters only when the target system and authorial intent support that distinction.
- Use true ordinal forms only when the font supports them and the language calls for them; never synthesize them by shrinking arbitrary letters.

## Whitespace `[COMP-005]`

- Use one word space between sentences in composed prose.
- Use nonbreaking spaces to keep required tokens together, including section or paragraph marks with their references and short figure labels with their numbers.
- Do not manufacture spacing with repeated spaces, tabs, or empty paragraphs. Use paragraph, layout, or table controls.
- Preserve whitespace in preformatted text, code, commands, and data.

## Alternate figures and accents `[COMP-006]`

Choose lining or oldstyle and proportional or tabular figures according to role: tables and aligned quantities generally need tabular figures; running prose may benefit from proportional or oldstyle figures if the font supplies them. Preserve accented characters in names and words; do not strip diacritics to fit a font. A missing glyph is a font-selection failure, not permission to alter the text.

## Parentheses, brackets, and braces `[COMP-007]`

Use parentheses for ordinary prose asides, brackets for editorial material inside quotations or for nested delimiters when necessary, and braces mainly for mathematical or technical notation. Keep pairs balanced, avoid piling nested asides into unreadable sentences, and preserve every delimiter in code, identifiers, legal references, and data. Apply surrounding punctuation according to the sentence's grammar rather than moving marks mechanically.

## Emphasis and caps `[TYPE-005]`

Use bold or italic as a single, restrained signal. Avoid bold-italic stacking and paragraph-length emphasis unless meaning requires it. Underlining is for links or a domain-specific convention, not generic emphasis. Use real small caps; for all-caps or small-caps runs, add modest tracking by visual calibration and keep long passages out of caps. Never letterspace lowercase prose as a generic effect.
```

## File: skills/typography/fonts.md
size: 3947
sha: 42364b78e59b70cc447fa549b3ddee1aa4bf95a5
upstream: https://github.com/danium/practicaltypography/blob/main/skills/typography/fonts.md

```text
# Fonts

Load this reference for selecting, pairing, validating, loading, or licensing fonts. The lists below are a selective working shortlist, not the full live Practical Typography font tables. Source-derived names were last checked on 2026-08-22; consult the linked registry before describing a current list as complete.

## Source shortlist `[FONT-001]`

Practical Typography treats professional fonts as a high-leverage upgrade and judges fonts in context rather than by serif versus sans alone.

- Useful system starting points named favorably by the source include Charter, Athelas, Avenir, Bell, Book Antiqua, Century Schoolbook, Franklin Gothic, Garamond, Gill Sans, Helvetica, Hoefler Text, Iowan Old Style, Optima, Palatino, Seravek, and Sitka.
- Source-endorsed free families include Charter, Source Serif, Source Code, Cooper Hewitt, IBM Plex, and Fira Mono.
- The source strongly discourages overexposed defaults and novelty or script faces for professional body text. Times New Roman, Arial, Comic Sans, Papyrus, and similar defaults should trigger a contextual review, not an automatic content-independent rejection.
- Screen-oriented faces can be appropriate on screen even when they are poor print choices. PDF typography should be evaluated for its likely viewing and printing contexts.

For the complete current system-font grades and professional alternatives, follow the Practical Typography pages recorded in [provenance.md](provenance.md).

## Validate the actual family `[FONT-002]`

A recommendation passes only after checking what the artifact requires:

- glyph repertoire for every language, symbol, accent, and emoji policy in the content;
- genuine weights, italics, and small caps where those styles are used;
- required OpenType behavior, including kerning and appropriate proportional, tabular, lining, oldstyle, fraction, or ordinal figures;
- legibility and metrics at the actual size, medium, and rendering engine;
- compatibility of fallback families, including line breaks and control dimensions;
- support in the target browser, office application, renderer, printer, or export path;
- the applicable desktop, web, app, redistribution, and document-embedding rights.

Do not strip accents, substitute characters, synthesize a missing style, or silently accept tofu to make a font pass. If PDF embedding is prohibited or technically unavailable, choose an embeddable alternative or an explicitly compliant delivery workflow.

## Pairing `[FONT-003]`

One family with a capable range is often enough. Two families are a practical maximum for most artifacts; add another only when a distinct role such as code requires it. Give each family a consistent role and switch at semantic boundaries. Contrast can come from structure and metrics, not merely serif versus sans. Families by the same designer or within a superfamily are a useful starting point, not a guarantee.

## Monospaced and code text `[FONT-004]`

Use monospaced type for code or genuinely columnar character data, not running body prose. Confirm that punctuation and confusable characters remain distinct. In reader-facing code, disable discretionary or programming ligatures and any substitution that conceals the typed sequence; preserving `!=`, `=>`, quotes, slashes, and backticks outranks stylistic joining. Standard prose ligatures are optional: consider them when the selected font has an actual collision, and never type ligature code points merely to force the effect.

## Project-authored screening rubric `[FONT-002]`

When a font is absent from the source, investigate its designer or foundry, family completeness, real styles, glyph and feature coverage, rendering quality, exposure in the intended context, licensing, and delivery support. Named contemporary families are examples to test, not endorsements. “Inter passes” and similar unconditional verdicts are retired because a family can pass one context and fail another.
```

## File: skills/typography/international.md
size: 2237
sha: ff24e4912d89fe4571707a35e09ae672d35286c9
upstream: https://github.com/danium/practicaltypography/blob/main/skills/typography/international.md

```text
# International and mixed-script typography

Load this reference whenever content is not exclusively English-language Latin text, or when language and script are unknown. The project's detailed punctuation and spacing rules are validated only for English in the Latin script `[INTL-001]`.

## Establish language and direction `[INTL-001]`

Identify the language, script, and direction for each meaningful run. Require correct metadata where the format supports it, such as document language, HTML `lang`, and directionality. Metadata enables pronunciation, hyphenation, line breaking, quotation marks, justification, and font fallback; visual appearance alone is not enough.

Do not infer language solely from script. Preserve personal names, loanwords, and mixed-language runs. Confirm editorial conventions when regional or house styles differ.

## Script-sensitive stop conditions `[INTL-002]`

Do not apply English rules for capitalization, word spaces, line breaking, hyphenation, justification, punctuation, quotation marks, emphasis, or letterspacing to an unfamiliar language or script. In particular:

- CJK line breaking and justification are not Latin word-spacing problems.
- Arabic and related scripts depend on joining and shaping; arbitrary tracking or character substitution can break words.
- Hebrew and Arabic mixed with Latin or numbers require bidirectional inspection, not source-order guesses.
- Thai, Khmer, Lao, and other scripts may not mark word boundaries with spaces.
- Accents, combining marks, emoji sequences, and variation selectors must remain intact.

Preserve unknown conventions, state the skill's limitation, and route to language-specific editorial guidance plus the W3C Internationalization layout index or another authoritative source. Render representative text with the chosen font and shaping engine before approving it.

## Mixed-script checks `[INTL-002]`

Verify glyph coverage, baseline and x-height compatibility, punctuation ownership, numeric style, fallback behavior, line breaking, justification, and direction at actual sizes. Use language-aware hyphenation only for correctly tagged languages. Never require global `hyphens: auto` as a universal fix for justified mixed-script text.
```

## File: skills/typography/layout.md
size: 3898
sha: 27c21d1d0ce97fc7b1419c532a14a7591b9d3583
upstream: https://github.com/danium/practicaltypography/blob/main/skills/typography/layout.md

```text
# Layout and document structure

Load this reference for paragraph systems, headings, lists, block quotations, tables, styles, pagination, columns, or grids. Numeric values are starting ranges unless the rule explicitly describes a semantic requirement.

## Body text and paragraphs `[TYPE-001] [TYPE-002] [TYPE-003]`

For English-language running prose, start with 15–25 px on the web or 10–12 pt in print, line spacing of 120–145%, and about 45–90 actual characters per rendered line. Font metrics and reading conditions matter, so adjust in the smallest visible increments and compare rendered alternatives. If size shrinks, reevaluate line spacing and measure too.

Signal paragraphs with either a first-line indent or paragraph space, not both. Do not indent the first paragraph after a heading or other obvious break. Avoid centered running prose. Justification is conditional: use it only when the language, line-breaking engine, hyphenation or other script-appropriate behavior, and column width produce even spacing without harming comprehension.

## Headings `[TYPE-004]`

Use as few heading levels as the structure needs. Create hierarchy with the smallest visible combination of position, weight, size, font, and spacing that works; no modular ratio is required. Space above should ordinarily exceed space below, and headings should remain with the following text. Avoid underlining, fake small caps, and excessive capitalization. Use automatic hierarchical numbering when numbering is necessary.

## Automated lists `[LAYOUT-001]`

Use the application's list feature or semantic HTML rather than typed bullets, tabs, or manual numbering. Align wrapped lines with the list text, keep punctuation and capitalization consistent, and avoid a list when ordinary prose would be clearer. Restart or continue numbering through list controls, not by editing visible numerals.

## Paragraph and character styles `[LAYOUT-002]`

Encode repeated roles as paragraph, character, or semantic styles. Equivalent elements should be identical and different roles materially distinct. Do not repair a system with repeated local formatting. Direct formatting is acceptable for isolated exceptions, not for the underlying hierarchy.

## Block quotations `[LAYOUT-003]`

Distinguish a block quotation structurally with indentation, spacing, a rule, or another restrained device; do not stack bold, italic, tint, and oversized quotation marks. Remove redundant quotation marks around a true block quotation. When editorial authority permits, quote only what is necessary, edit with proper attribution conventions, or integrate short quotations into prose.

## Tables `[MEDIA-005]`

Typography should expose the data's logic. Align quantities by their numeric meaning, identifiers according to how they are read, and labels only after the data columns work. Use appropriate numeric features, adequate cell padding, and thin rules or whitespace rather than decoration. Do not force an arbitrary scale ratio; calibrate type so labels and values remain readable in the delivery format.

## Pagination and page flow `[LAYOUT-004]`

Use keep-with-next on headings and apply widow/orphan control when the actual pages need it. Create page breaks with a single page-break control, never stacked returns. Use spacing properties rather than empty paragraphs. In multi-column layouts, keep baselines and paragraph spacing coherent when the design requires alignment, and inspect every final page.

## Columns, grids, rules, and whitespace `[LAYOUT-005]`

Let rendered measure determine column width. Relate new elements to existing alignments and use a grid where it clarifies those relationships. Prefer whitespace before borders; when a rule is needed, keep it subordinate to the text. Asymmetry should look intentional, not accidental. Work outward from the text instead of inward from arbitrary page edges.
```

## File: skills/typography/media.md
size: 5005
sha: 3110d5bd7f2687cedab5e20c352080ac1a31a9c3
upstream: https://github.com/danium/practicaltypography/blob/main/skills/typography/media.md

```text
# Medium-specific typography

Load only the section matching the artifact. Combine this file with [layout.md](layout.md), [fonts.md](fonts.md), [web.md](web.md), or [international.md](international.md) when those concerns are material.

## Print documents `[MEDIA-001]`

- Start with 10–12 pt body text, 120–145% line spacing, black text, and a print-suitable font; judge the rendered page rather than the nominal point size alone.
- Let line length determine margins. On US Letter, 1-inch side margins are often too small for 12 pt proportional body text, but any inch value is subordinate to rendered measure and the binding or production context.
- Use two or three columns only when the content, page, and reading order support them. Inspect baseline and paragraph-spacing behavior rather than enforcing a universal grid.
- Use keep-with-next for headings, apply widow/orphan control where actual page flow needs it, and create breaks and spacing with document controls rather than empty returns.
- Fit a page by revisiting spacing, measure, editing, and structure together. Never reduce type until the text technically fits without inspecting readability.

## Presentations `[MEDIA-002]`

Slides are viewed at distance and must be calibrated in the actual room or a realistic preview.

- Select a stable base size by fitting roughly 12–15 lines as a calibration test, then place far less text on each real slide. Keep equivalent roles consistent, disable automatic shrinking, and edit content when it does not fit.
- Prefer short, left-aligned text blocks and generous empty space. Centering can suit a single short statement but not paragraph-like slide copy.
- In dark rooms, begin with a genuinely dark background and raise text luminance only as far as legibility and contrast require; inspect the projector because screen colors do not predict projected light. In lit rooms, reduce glare while maintaining required contrast.
- Use a small set of roles such as title, body, and attribution. Exact pixel sizes, title ratios, and tracking values are project calibration choices, not source mandates.

## Email and collaborative documents `[MEDIA-003]`

Email rendering and font availability are unpredictable. Prefer robust system stacks and simple spacing, or plain text when reliability matters more than styling. Contact information should remain selectable text. In collaborative or editable documents, a widely available system font can be the correct choice even when a professional font would look better locally; editability and faithful interchange outrank exclusivity.

## Resumes `[MEDIA-004]`

Do not cram a resume merely to force one page. Put decisive information early, keep labels subordinate to substance, use calm lists, and verify the exported PDF. Delivery requirements may impose a page count, applicant-tracking constraints, or a mandated template; honor those constraints before aesthetic preferences. Proofread content separately from the typography audit.

## Tables of numbers `[MEDIA-005]`

- Use tabular figures where vertically aligned digits need equal advances; choose lining or oldstyle figures according to the surrounding role.
- Align quantities so equal numeric places line up. Preserve meaningful leading and trailing zeros and use locale-appropriate grouping and decimal separators.
- Treat identifiers such as postal codes differently from quantities. Do not imply arithmetic meaning through alignment or padding.
- Format labels after the data columns work. Use adequate padding and restrained rules so the data, not decoration, dominates.
- Type size, rule weight, and cell ratios must be calibrated in the delivery medium; previous exact supporting-element ratios are retired as unsupported precision.

## PDF production `[MEDIA-006]`

Prefer direct PDF generation or a controlled export path over printing through an incidental driver. At final delivery, verify:

- every page is visually complete at normal and enlarged inspection;
- text intended as text remains searchable, selectable, and correctly ordered;
- required fonts are embedded or validly substituted, with licenses permitting the chosen workflow;
- links, bookmarks, tags, language metadata, and accessibility structure survive when required;
- color, transparency, image resolution, page boxes, and print behavior suit the destination;
- no reflow, missing glyph, fallback, clipping, blank page, widow, or orphan appeared during export.

An editable source or successful export command is not final-PDF evidence. Inspect the delivered file itself.

## General layout maxims `[CORE-001]`

Start with body text. Make foreground and background roles clear. Adjust in the smallest visible increments and compare alternatives. Keep equivalent elements consistent and different elements visibly different. Relate new elements to an existing alignment system. Prefer simplicity and useful whitespace. Learn from typography that succeeds in the same medium, then work outward from the text.
```

## File: skills/typography/provenance.md
size: 15211
sha: 4a30bdb205d17db388376e7197049c78c2f13134
upstream: https://github.com/danium/practicaltypography/blob/main/skills/typography/provenance.md

```text
# Rule provenance registry

This file is the source of truth for normative rule clusters in the typography skill. Classifications are:

- `PT`: paraphrased from Matthew Butterick's *Practical Typography*;
- `DEVIATION`: a deliberate project-authored heuristic or workflow choice;
- `CURRENT`: a current accessibility, internationalization, platform, semantic, or legal requirement from another authority.

`Scope` describes where the rule applies. `Evaluations` point to scenario IDs in `../../evals/scenarios.json`. Source pages and external standards were verified on **2026-08-22** unless an entry says otherwise. The registry stores paraphrases and page identities, not source prose.

| Rule ID | Class | Normalized recommendation and scope | Source or rationale | Evaluations |
|---|---|---|---|---|
| CORE-001 | PT | Start with body text; calibrate in small visible increments; compare alternatives; preserve consistency, simplicity, relationships, and whitespace. All media. | [Summary of key rules](https://practicaltypography.com/summary-of-key-rules.html) and [Typography in ten minutes](https://practicaltypography.com/typography-in-ten-minutes.html) | EVAL-PRINT, EVAL-SLIDES |
| CORE-002 | CURRENT | Correctness, accessibility, language, and legal constraints outrank aesthetics; user intent and medium outrank optional benchmarks and presets. All content. | Project safety ordering required to prevent destructive or noncompliant advice; supported by the standards entries below. | EVAL-CODE, EVAL-WCAG, EVAL-NONLATIN, EVAL-FONT |
| AUDIT-001 | DEVIATION | Classify medium, role, intent, language/script, and access to rendering before applying rules. Audit workflow. | Prevents body-prose guidance from being applied to code, display, data, and unfamiliar scripts. | EVAL-WEB-PROSE, EVAL-CODE, EVAL-MIXED |
| AUDIT-002 | DEVIATION | Protect literal and semantic spans before character transformations. All editable content. | Typed transformation gate introduced after baseline rules could corrupt code, measurements, email, and legal references. | EVAL-CODE, EVAL-EMAIL |
| AUDIT-003 | DEVIATION | Distinguish source, computed/application, rendered, and final-delivery evidence. All audits. | Prevents claims about outcomes that were never inspected. | EVAL-RESPONSIVE, EVAL-WEBFONT, EVAL-PDF |
| AUDIT-004 | DEVIATION | Audit body text, paragraphs, headings, emphasis, composition, and supporting elements in reader-impact order. General audits. | Project workflow derived from the source's emphasis on body text and tested for actionable output. | EVAL-WEB-PROSE |
| AUDIT-005 | DEVIATION | Report contextual severity, a correction, evidence level, and the top three fixes. General audits. | Preserves the project's useful reporting contract without attributing its severity taxonomy to Butterick. | EVAL-WEB-PROSE, EVAL-DEMO |
| ROUTE-001 | DEVIATION | Load only focused references needed for the medium, content, and risk class. Skill activation. | Keeps the entry skill compact while preventing specialized advice without its safety reference. | EVAL-CODE, EVAL-PDF, EVAL-NONLATIN |
| TYPE-001 | PT | English running prose: 15–25 px web or 10–12 pt print, 120–145% line spacing, about 45–90 rendered characters; verify measure from rendered text. | [Point size](https://practicaltypography.com/point-size.html), [Line spacing](https://practicaltypography.com/line-spacing.html), [Line length](https://practicaltypography.com/line-length.html), [Responsive web design](https://practicaltypography.com/responsive-web-design.html) | EVAL-WEB-PROSE, EVAL-RESPONSIVE, EVAL-PRINT |
| TYPE-002 | PT | Use first-line indents or paragraph space, not both; avoid empty returns as spacing. English prose. | [First-line indents](https://practicaltypography.com/first-line-indents.html), [Space between paragraphs](https://practicaltypography.com/space-between-paragraphs.html) | EVAL-WEB-PROSE, EVAL-PRINT |
| TYPE-003 | PT | Do not center running prose; justify only when line breaking and spacing are acceptable. Latin prose, subject to script rules. | [Centered text](https://practicaltypography.com/centered-text.html), [Justified text](https://practicaltypography.com/justified-text.html), [Hyphenation](https://practicaltypography.com/hyphenation.html) | EVAL-WEB-PROSE, EVAL-MIXED |
| TYPE-004 | PT | Use restrained heading levels and the smallest visible hierarchy; space above exceeds below; keep headings with following text. Documents and web prose. | [Headings](https://practicaltypography.com/headings.html) | EVAL-WEB-PROSE, EVAL-PRINT |
| TYPE-005 | PT | Use restrained bold/italic, avoid generic underlining, use real small caps, track caps visually, and do not letterspace lowercase prose. Latin text roles. | [Bold or italic](https://practicaltypography.com/bold-or-italic.html), [Underlining](https://practicaltypography.com/underlining.html), [All caps](https://practicaltypography.com/all-caps.html), [Letterspacing](https://practicaltypography.com/letterspacing.html) | EVAL-WEB-PROSE, EVAL-SLIDES |
| COMP-001 | PT | Use language-appropriate curly quotes and apostrophes in eligible prose while preserving straight measurement and literal marks. English prose. | [Straight and curly quotes](https://practicaltypography.com/straight-and-curly-quotes.html) and [Foot and inch marks](https://practicaltypography.com/foot-and-inch-marks.html) | EVAL-CODE, EVAL-EMAIL |
| COMP-002 | PT | Distinguish hyphens, en dashes, em dashes, and minus signs by meaning. English prose and numeric ranges. | [Hyphens and dashes](https://practicaltypography.com/hyphens-and-dashes.html) | EVAL-WEB-PROSE, EVAL-CODE |
| COMP-003 | PT | Use an ellipsis character and intentional adjacent spacing in eligible prose; preserve literal periods elsewhere. English prose. | [Ellipses](https://practicaltypography.com/ellipses.html) | EVAL-WEB-PROSE, EVAL-CODE |
| COMP-004 | PT | Use copyright/trademark, multiplication/minus, measurement, and ordinal characters only when semantics and font support are known. Latin prose, measurements, and marks. | [Trademark & copyright symbols](https://practicaltypography.com/trademark-and-copyright-symbols.html), [Math symbols](https://practicaltypography.com/math-symbols.html), [Ordinals](https://practicaltypography.com/ordinals.html) | EVAL-EMAIL, EVAL-FONT |
| COMP-005 | PT | Use one sentence space and semantic nonbreaking spaces; never fake layout with repeated spaces or returns. Composed prose and documents. | [One space between sentences](https://practicaltypography.com/one-space-between-sentences.html), [Nonbreaking spaces](https://practicaltypography.com/nonbreaking-spaces.html) | EVAL-EMAIL, EVAL-PRINT |
| COMP-006 | PT | Choose figure styles by role and preserve accents; missing glyphs require a font fix. Latin/mixed prose and numbers. | [Alternate figures](https://practicaltypography.com/alternate-figures.html), [Accented characters](https://practicaltypography.com/accented-characters.html) | EVAL-TABLES, EVAL-FONT |
| COMP-007 | PT | Use parentheses, brackets, and braces according to prose or technical role; balance pairs and preserve literal delimiters. English prose and protected literal content. | [Parentheses, brackets, and braces](https://practicaltypography.com/parentheses-brackets-and-braces.html) | EVAL-CODE, EVAL-EMAIL |
| LAYOUT-001 | PT | Use automated or semantic lists rather than typed markers and manual numbering. Documents and web. | [Bulleted and numbered lists](https://practicaltypography.com/bulleted-and-numbered-lists.html) | EVAL-PRINT |
| LAYOUT-002 | PT | Encode repeated roles with paragraph, character, or semantic styles rather than repeated local formatting. Documents and web systems. | [Paragraph and character styles](https://practicaltypography.com/paragraph-and-character-styles.html) | EVAL-PRINT |
| LAYOUT-003 | PT | Distinguish block quotations structurally, remove redundant quotation marks, and edit or integrate where authorized. Documents and web prose. | [Block quotations](https://practicaltypography.com/block-quotations.html) | EVAL-WEB-PROSE |
| LAYOUT-004 | PT | Use page-flow controls, not stacked returns; inspect actual pagination and columns. Paginated documents. | [Hard page breaks](https://practicaltypography.com/hard-page-breaks.html), [Widow and orphan control](https://practicaltypography.com/widow-and-orphan-control.html), [Columns](https://practicaltypography.com/columns.html), [Grids](https://practicaltypography.com/grids.html) | EVAL-PRINT, EVAL-PDF |
| LAYOUT-005 | PT | Derive layout from text, align related elements, and prefer whitespace before rules. All visual media. | [Page layout](https://practicaltypography.com/page-layout.html), [Rules & borders](https://practicaltypography.com/rules-and-borders.html) | EVAL-PRINT, EVAL-SLIDES, EVAL-TABLES |
| FONT-001 | PT | Treat the local font names as a dated shortlist; select source-favored or professional alternatives in context. Latin-centric source list. | [System fonts](https://practicaltypography.com/system-fonts.html), [Free fonts](https://practicaltypography.com/free-fonts.html), [Font recommendations](https://practicaltypography.com/font-recommendations.html) | EVAL-FONT, EVAL-PRINT |
| FONT-002 | CURRENT | Validate glyphs, real styles, required features, fallbacks, application support, and license/embedding rights. All fonts and delivery media. | [CSS Fonts Module Level 4](https://www.w3.org/TR/css-fonts-4/) and [The copyright status of fonts](https://practicaltypography.com/the-copyright-status-of-fonts.html); no visual recommendation can grant font rights. | EVAL-FONT, EVAL-PDF, EVAL-WEBFONT |
| FONT-003 | PT | Prefer a restrained family count and stable semantic roles; designer/superfamily matching is a shortcut, not a law. General artifacts. | [Mixing fonts](https://practicaltypography.com/mixing-fonts.html) | EVAL-WEB-PROSE, EVAL-PRINT |
| FONT-004 | PT | Use monospaced faces for code; prose ligatures are contextual, while reader-facing code must expose literal characters. Code and Latin prose. | [Monospaced fonts](https://practicaltypography.com/monospaced-fonts.html), [Ligatures](https://practicaltypography.com/ligatures.html), and [Ligatures in programming fonts: hell no](https://practicaltypography.com/ligatures-in-programming-fonts-hell-no.html) | EVAL-CODE |
| WEB-001 | CURRENT | Separate declared, computed, loaded, rendered, and delivered web typography. Web. | Browser rendering reality; [CSS Fonts Module Level 4](https://www.w3.org/TR/css-fonts-4/) defines font matching and use. | EVAL-WEBFONT, EVAL-RESPONSIVE |
| WEB-002 | PT | Treat `ch` as a width heuristic and verify actual rendered characters at material viewports. Web prose. | [Responsive web design](https://practicaltypography.com/responsive-web-design.html) | EVAL-RESPONSIVE |
| WEB-003 | CURRENT | Test resilience under WCAG text-spacing override values without loss of content or functionality. Web. | [WCAG 2.2 Understanding SC 1.4.12](https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html) | EVAL-WCAG |
| WEB-004 | CURRENT | Typography must preserve contrast, zoom/reflow, overflow, and interaction cues. Web. | [WCAG 2.2](https://www.w3.org/TR/WCAG22/) | EVAL-WCAG |
| WEB-005 | CURRENT | Inspect webfont loading, fallback metrics, layout shift, variable axes, genuine styles, and optical sizing. Web. | [CSS Fonts Module Level 4](https://www.w3.org/TR/css-fonts-4/) and [font-optical-sizing](https://developer.mozilla.org/docs/Web/CSS/font-optical-sizing) | EVAL-WEBFONT |
| INTL-001 | CURRENT | Declare correct language and direction; English-Latin rules are scoped, not universal. International content. | [Why use the language attribute?](https://www.w3.org/International/questions/qa-lang-why) and [Language Enablement Index](https://www.w3.org/International/typography/) | EVAL-NONLATIN, EVAL-MIXED |
| INTL-002 | CURRENT | Preserve unfamiliar script behavior and use script-specific line breaking, justification, spacing, punctuation, and shaping guidance. International and mixed-script content. | [W3C Language Enablement Index](https://www.w3.org/International/typography/) | EVAL-NONLATIN, EVAL-MIXED, EVAL-FONT |
| MEDIA-001 | PT | Calibrate print body text, measure, columns, and page flow on rendered pages. Print. | [Body text](https://practicaltypography.com/body-text.html), [Page margins](https://practicaltypography.com/page-margins.html), [Columns](https://practicaltypography.com/columns.html), [Grids](https://practicaltypography.com/grids.html) | EVAL-PRINT |
| MEDIA-002 | PT | Calibrate slide type at viewing distance, keep roles stable, edit instead of auto-shrinking, and evaluate projected contrast. Presentations. | [Presentations](https://practicaltypography.com/presentations.html) | EVAL-SLIDES |
| MEDIA-003 | PT | Prefer robust system typography for email and collaborative documents when portability matters. Email and editable collaboration. | [Emails](https://practicaltypography.com/emails.html) and [System fonts](https://practicaltypography.com/system-fonts.html) | EVAL-EMAIL |
| MEDIA-004 | PT | Do not cram resumes; prioritize content and verify PDF delivery under applicable constraints. Resumes. | [Résumés](https://practicaltypography.com/resumes.html) | EVAL-PDF |
| MEDIA-005 | PT | Make numeric typography reflect data meaning; use suitable figures, alignment, spacing, and restrained rules. Tables. | [Tables](https://practicaltypography.com/tables.html) | EVAL-TABLES |
| MEDIA-006 | PT | Generate PDF through a controlled path and inspect searchable text, embedded fonts, and final pages. PDF delivery. | [How to make a PDF](https://practicaltypography.com/how-to-make-a-pdf.html) | EVAL-PDF |
| PRESET-001 | DEVIATION | Offer Bookish, Airy screen, and Compact docs as optional starting points, then calibrate visually. English body prose. | Project convenience presets. They are not source ranges or publication measurements. | EVAL-WEB-PROSE |

## Resolved legacy claims

The baseline revision was `41559fe7ee3c27c4fc46a6feda29ad7898c7b4c6`. Every previously unclassified normative cluster was mapped above or retired:

- `45–90ch` as literal character count → replaced by actual-character verification (`TYPE-001`, `WEB-002`).
- Ligatures on by default → replaced by collision-dependent prose guidance and literal code protection (`FONT-004`).
- Fixed heading ratio `1.6 / 1.25 / 1.0` and exact supporting-element ratios → retired as unsupported source precision (`TYPE-004`, `MEDIA-002`, `MEDIA-005`).
- Unconditional quote, `(c)`, dash, ellipsis, and whitespace conversion → gated by content type and semantic intent (`AUDIT-002`, `COMP-001..005`).
- “Full” system-font list → corrected to a dated shortlist (`FONT-001`).
- Unconditional “Inter passes” and feature checklists attributed to the source → replaced with a project-authored, context-dependent validation rubric (`FONT-002`).
- Fixed slide pixel ranges and exact callout, code, caption, navigation, table, and rule ratios → replaced by medium calibration or explicitly scoped starting points.

No unresolved authority or scope flags remain. Add a registry entry and an evaluation mapping before adding new normative guidance.
```

## File: skills/typography/web.md
size: 3306
sha: c65760f5236744fc3dbd451ec011e09ccf697240
upstream: https://github.com/danium/practicaltypography/blob/main/skills/typography/web.md

```text
# Web typography

Load this reference for browser-rendered text, responsive layouts, webfonts, variable fonts, or accessibility verification. Combine it with [composition.md](composition.md) for literal text and [international.md](international.md) for non-English or mixed-script content.

## Declarations are not outcomes `[WEB-001]`

Record the strongest evidence available:

1. authored HTML/CSS;
2. computed styles and the font actually used for representative glyphs;
3. rendered lines at supported viewport widths and states;
4. captured or exported delivery evidence.

A declared family does not prove that the font loaded. A CSS width does not prove readable measure. A valid layout at one viewport does not prove responsive behavior. Label source-only findings provisional.

## Responsive measure `[WEB-002]`

For English running prose, use about 45–90 actual characters per rendered line as the Practical Typography benchmark. `ch` measures the advance width of `0`, so `max-width: 60ch` is a convenient initial estimate, not evidence of 60 characters. Count representative rendered lines at material breakpoints or use the lowercase alphabet test: roughly two to three alphabets per line.

Check narrow, typical, and wide supported viewports; also inspect enlarged text and fallback-font states. Prevent prose from running edge to edge merely because a viewport is wide. Display headings, navigation, code, and tables have different measure requirements.

## Accessibility resilience `[WEB-003] [WEB-004]`

Accessibility outranks aesthetic tuning. Verify that content and functionality survive at least the WCAG 2.2 text-spacing test values without clipping, overlap, truncation, obscuring controls, or loss of information:

- line height at least 1.5 times the font size;
- paragraph spacing at least 2 times the font size;
- letter spacing at least 0.12 times the font size;
- word spacing at least 0.16 times the font size.

These are override test values, not mandatory default styling. Also test relevant contrast, browser zoom or text enlargement, reflow, overflow, focus visibility around styled links, and user preference settings. Do not solve overflow by disabling zoom, hiding text, or forcing an unreadably small size.

## Fonts, fallbacks, and stability `[WEB-005]`

- Verify network success, font decoding, and the actual face used for body, emphasis, headings, symbols, and required scripts.
- Choose a loading policy appropriate to the content. Report disruptive flashes, invisible text, late swaps, or layout shift when they materially affect reading.
- Build a metrically compatible fallback stack where practical; compare line breaks, control sizes, and cumulative layout shift in fallback and loaded states.
- For variable fonts, verify required axes and instance ranges. If an optical-size axis exists, confirm that automatic `font-optical-sizing` or an explicit setting is suitable at the rendered sizes.
- Confirm that synthetic bold or italic is not silently replacing required genuine styles.

## Interaction conventions `[WEB-004]`

Keep links identifiable without relying on color alone, and avoid styling noninteractive text so it is easily mistaken for a link. Preserve selectable, searchable text. Typography must not hide status, validation, or control labels.
```

## File: README.md
upstream: https://github.com/danium/practicaltypography/blob/main/README.md

````text
# practicaltypography

**Your agent already knows typography rules. It doesn't know which ones matter, in what order, or when you're allowed to break them.**

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
![Skills: 1](https://img.shields.io/badge/skills-1-blue.svg)

One skill that audits and produces publication-grade typography for blogs, websites, docs, slides, résumés, data tables, and PDFs — grounded in Matthew Butterick's *Practical Typography* and separated from project-authored heuristics and current accessibility, internationalization, font, and delivery requirements. Its gated audit classifies context, protects literal content, inspects the strongest available evidence, applies higher-priority constraints, then reports the most consequential corrections.

![Magazine-style cover: TYPOGRAPHY masthead, cover line NO-AI-SLOP, and stacked cover lines describing the skill.](assets/social-preview.png)

---

## The demo

Same agent. Same prompt. One of them read the skill first.

> **Prompt:** *"My blog looks unprofessional and I can't figure out why. Can you audit the typography?"* — with CSS: 14px Open Sans/Arial, `line-height: 1.8`, full-width column, indent + margin on paragraphs, justified, uppercase underlined headings, bold-italic blockquotes.

<table>
<tr>
<th width="50%">Any agent, vanilla</th>
<th width="50%">Same agent, <code>typography</code></th>
</tr>
<tr valign="top">
<td>

A solid 8-point list: 14px too small ("use 16–18px"), unconstrained line length ("readable 45–75 characters"), uppercase + underlined headings, justify rivers, redundant paragraph separation, bold+italic blockquotes, "line-height 1.5–1.65 at 16px+ reads better", straight quotes.

*(All real issues. No order, no severity, no verdict on the fonts — Arial sat in that stack unremarked. The numbers are vibes: 45–75, 1.5–1.65, "ideally 1.125rem+".)*

</td>
<td>

`[MAJOR]` body font-size: 14px below range → **18px** (15–25px)
`[MAJOR]` line-height: 1.8 far above 1.2–1.45 → **1.4** — *"if you deliberately want an airy Medium-style feel, the pairing is 19–21px with 1.5–1.6, never 14px with 1.8"*
`[MAJOR]` measure: uncapped, 150+ chars on desktop → `max-width: 65ch` — *"the single most common web typography failure"*
`[MAJOR]` font stack: **Arial is an avoid-list font**; Open Sans judged overexposed by the unlisted-font criteria → Source Serif / Charter / IBM Plex

…then paragraphs, headings, emphasis, characters — each `[MAJOR|MINOR]`, closing with a corrected CSS block and **"the three fixes doing the most damage."**

</td>
</tr>
</table>

The vanilla answer isn't bad. It's *good* — and it missed the font entirely, ranked nothing, and its numbers drift with whatever the model last read. The skill's answer is a procedure: six checks in impact order, severity by definition rather than vibes, sourced ranges, and a required closing the user can act on.

---

## Before / after

The committed input [`demo/before.html`](demo/before.html) is audited in [`demo/AUDIT.md`](demo/AUDIT.md), and [`demo/after.html`](demo/after.html) applies the changes with the wording preserved. Character-composition edits are reported explicitly. [`demo/RUN.md`](demo/RUN.md) records the visual inspection context and artifact hashes; the broader behavior contract is scenario `EVAL-DEMO` in [`evals/scenarios.json`](evals/scenarios.json).

<table>
<tr>
<th width="50%">Before — vanilla agent</th>
<th width="50%">After — typography skill</th>
</tr>
<tr valign="top">
<td><img src="assets/demo-before.png" alt="Vanilla agent blog page: 16px Georgia at line-height 1.7, italic intro paragraph, tinted italic blockquote, dark striped table header, centered inverse closing box."></td>
<td><img src="assets/demo-after.png" alt="Same page after the skill: 18px Charter at line-height 1.4, roman intro, structural blockquote, quiet table with thin rules, left-aligned closing."></td>
</tr>
</table>

The headline changes: 16px/1.7 Georgia became 18px/1.4 Charter, the dark striped table header became thin rules with tabular figures, the italic intro and tinted blockquote calmed down to structural distinction, and the centered inverse closing box became left-aligned text. Same content — and the page got *shorter* (1584px vs 1804px of scroll), because tighter leading recovers what the web-default 1.7 wastes. Good typography costs nothing in word count.

---

## Install

**Any agent (recommended):**

```bash
npx skills add danium/practicaltypography
```

**Claude Code (plugin):**

```
/plugin marketplace add danium/practicaltypography
/plugin install practicaltypography@practicaltypography
```

**Codex:** ask `$skill-installer` to install from `https://github.com/danium/practicaltypography`

**Manual:** clone and copy `skills/typography` into your agent's skills directory.

---

## What's inside

| File | Covers |
|---|---|
| [`SKILL.md`](skills/typography/SKILL.md) | Compact router, precedence order, gated audit, impact ordering, evidence levels, reporting contract, and optional project presets |
| [`composition.md`](skills/typography/composition.md) | Safe transformations, literal-content protection, punctuation, whitespace, symbols, figures, accents, emphasis, and caps |
| [`layout.md`](skills/typography/layout.md) | Body text, paragraphs, headings, automated lists, semantic styles, block quotations, tables, page flow, columns, and grids |
| [`fonts.md`](skills/typography/fonts.md) | A dated source shortlist plus context-sensitive validation for glyphs, genuine styles, features, fallbacks, application support, and licensing |
| [`web.md`](skills/typography/web.md) | Declared-versus-rendered evidence, responsive measure, WCAG resilience, actual font loading, fallback metrics, variable axes, and optical sizing |
| [`media.md`](skills/typography/media.md) | Print, slides, email and collaboration, résumés, numeric tables, direct PDF production, and final-delivery checks |
| [`international.md`](skills/typography/international.md) | English-Latin scope, language and direction metadata, script-sensitive stop conditions, and mixed-script verification |
| [`provenance.md`](skills/typography/provenance.md) | Stable rule IDs classified as `PT`, `DEVIATION`, or `CURRENT`, with sources, scope, freshness, and evaluation mappings |
| [`evals/`](evals/README.md) | Fourteen versioned risk scenarios, minimal fixtures, observable rubric, baseline/candidate results, and source-drift review |

## Pick your entry point

| Situation | Where the skill takes it |
|---|---|
| "This page/deck looks unprofessional" | Gated audit, findings ranked `[MAJOR\|MINOR]`, corrected values, evidence level, and top-three fixes |
| "Set up typography for my blog / docs site" | Body benchmark plus focused composition, layout, font, and web references |
| "Make it airy like Medium, not like a book" | Preference protocol: intent governs, reference beats quoted number, named presets (Bookish · Airy modern web · Compact docs) |
| "Style my conference slides" | Viewing-distance calibration, stable role sizes, contrast checks, and editing instead of auto-shrink |
| "Which font should I use?" | Dated source shortlist plus glyph, style, feature, fallback, support, and license validation |
| "My data tables look off" | Numeric features, alignment by number *kind*, precision preservation, and medium calibration |
| "Can I ship this PDF?" | Direct export, searchable text, font embedding and rights, metadata, and final-page inspection |
| "Audit this Arabic/Japanese/mixed-script text" | Language metadata, preservation gates, authoritative routing, and rendered script checks |

---

## How it was built

The repository now carries a vendor-neutral regression suite. Fourteen scenarios cover web prose, responsive measure, code, email, print, slides, tables, PDF delivery, font fallback, WCAG text spacing, non-Latin and mixed-script text, font licensing and glyph coverage, and public evidence. The baseline result records what revision `41559fe7e
````
