Better Typography

Great typography

Good typography is mostly restraint. A sensible scale, comfortable spacing and enough contrast beat any clever effect. A label, a table cell, a marketing headline and an article paragraph should not share one set of rules. Apply these principles when building or reviewing anything with text in it.

Adapted from Jakub Krehel's better-typography at commit a67333399dabbc71d7778962cb9c4fb9b86a00d0.

When reviewing, read the page instead of scanning the code: squint to check the hierarchy holds, read one full paragraph for comfort, and resize the viewport to catch bad wrapping, widows and truncation at real content lengths.

The words themselves (button labels, error messages, empty states) are covered by the better-writing skill; semantic heading structure by better-accessibility; spatial RTL layout and logical CSS properties by better-layout; rendered-pair contrast measurement and color remediation by oklch-skill. This skill owns how text renders, wraps, and behaves in mixed-direction content.

Match the project's styling system. Before suggesting or writing any fix, check how the codebase styles things and express every change in that system: Tailwind utilities in a Tailwind project, plain declarations in CSS, CSS Modules, styled-components or StyleX. The cheat sheet maps each declaration to its Tailwind equivalent. Never introduce a second styling approach just to apply a typography fix.

Quick Reference

Core Principles

1. Serve the Right Format

Use .woff2 (Brotli compression, broadly supported) on the web. .woff is a fallback only for very old browsers; .ttf and .otf are raw desktop formats with no web compression. How the files are loaded is the project's own concern, this skill does not prescribe it.

2. Properties Over Raw Tags

When a CSS property exists, use it. font-weight: 650 instead of font-variation-settings: "wght" 650, font-optical-sizing: auto instead of "opsz", font-variant-numeric: tabular-nums instead of font-feature-settings: "tnum" 1. Properties keep working when a non-variable fallback renders. Reserve the raw-tag properties for custom axes ("GRAD" 80) and niche features ("ss01" 1) that have no property of their own.

3. Load Intended Weights and Styles

Browsers may synthesize a requested weight or style that the active family does not provide. Prefer loading the faces the design actually uses. Set font-synthesis: none only after verifying that every required bold, italic, small-cap, superscript, and subscript form remains visually distinct across the complete fallback stack; disabling synthesis is not a diagnostic and must not erase emphasis.

4. Fewer Fonts, Sizes and Weights

Rarely use more than three fonts. Weight and size define hierarchy, but overusing them hurts readability quickly. Pair for contrast, not similarity: a serif headline with a sans body reads as deliberate, two near-identical sans-serifs read as a mistake. Below 18px, stay at weight 400+; weights under 300 are display-only (28px+), they disappear at text sizes.

5. Use a Type Scale with Semantic Names

Define a small set of sizes and deviate from it as little as possible. Hard-coded sizes without a system break down at scale. For solo projects, default names like text-sm work fine as long as the usage rules are clear. On a team, name sizes by use (text-body-sm), not by size, so the rules stay consistent.

6. Heading Sizes Descend with Level

Within a coherent page hierarchy, map heading levels to descending steps of the type scale: a visually subordinate heading should not accidentally overpower its parent. Adjacent levels may share a size toward the small end of the scale as long as weight or spacing keeps them distinct. Pick semantic heading elements according to better-accessibility; this skill controls only their visual treatment.

7. Line-Height by Role

Headings tighter, around 1.1. Body copy 1.5 to 1.6. Prefer unitless values so line-height scales with the font size; fixed values like 24px do not. Tight line-height is for short text: anything that wraps to three or more lines needs at least 1.4, even in height-constrained rows.

8. Letter-Spacing by Size

Large headings often look better with slightly negative letter-spacing. Small uppercase labels need a little positive letter-spacing so letters do not feel crowded. Body copy at reading sizes needs neither.

9. Cap the Measure

Long lines make it hard for the eye to find the next line. Cap long-form text around 60–75 characters per line. Any unit works: 65ch measures characters directly, and a pixel or rem cap is just as good: at a 16px body size the range lands roughly between 560px and 680px depending on the font, so Tailwind's max-w-xl or max-w-2xl fit. What matters is that a cap exists and the resulting line length sits in range.

10. Wrap Deliberately

text-wrap: balance distributes short text evenly across lines: use it on headings and short descriptions when the intended result is an even rag. Chromium ignores it after roughly six lines, so it is safe but ineffective on long-form text. Use text-wrap: pretty on known long-form copy when the goal is preventing a single-word final line; it does not repair every short two-word rag. Use overflow-wrap: break-word where long words, links, or IDs could escape the container, and white-space: nowrap where a label or badge should never break.

11. Tabular Numbers on Changing Values

Digits have different widths by default, so timers, counters and prices shift layout as they update. Apply font-variant-numeric: tabular-nums to any value that changes.

12. Truncate Without Losing Content

Single line: text-overflow: ellipsis with overflow: hidden and white-space: nowrap. Multiple lines: line-clamp. Truncation hides content, so if the missing text matters, keep the full value reachable in a tooltip or expanded view.

13. Write Copy Naturally, Style with CSS

Store text in natural case and control presentation with text-transform, so redesigns never require rewriting copy. Use smart punctuation: curly quotes in prose (straight quotes in code), an en dash for ranges like 2010–2020, an em dash to set off a thought, the single ellipsis character,   to keep values like 16 px together and ­ to control where long words may break.

14. Underlines from the Font

Default underlines sit wherever the browser decides. Pull position and thickness from the font's own metrics with text-underline-position: from-font and text-decoration-thickness: from-font, or tune manually with text-decoration-thickness, text-underline-offset and text-decoration-skip-ink. text-decoration-style draws the line dotted, dashed or wavy; a dotted underline is a common hint that a word carries extra information, like an abbreviation or a defined term. Unless the only thing animating is a color change, build the underline as a separate element instead of using text-decoration: color is the only part of a real underline that animates reliably.

15. Inputs at 16px on Mobile

iOS Safari zooms the whole page when an input's text is smaller than 16px. Keep input text at 16px on mobile viewports (text-base sm:text-sm). Avoid the maximum-scale=1 viewport meta: Safari ignores it for pinch zoom, but every other browser honors it and blocks zooming, which fails WCAG.

16. Size and Contrast Floors

Start long-form body text near the browser default of 16px, then judge it in the actual typeface, measure, platform, and product density. UI text can go smaller: 14px is a useful starting point for inputs and menus (inputs still need 16px on mobile, see principle 15), 13px for captions, rarely below 12px. When text appears low-contrast, use oklch-skill to measure the rendered pair and better-accessibility to classify the requirement; do not change colors unless asked.

17. Font Smoothing on the Root

On macOS text renders heavier than intended. Apply -webkit-font-smoothing: antialiased and -moz-osx-font-smoothing: grayscale (both covered by Tailwind's antialiased) once on the root layout so they cover all text.

18. Language and Bidi Behavior

Set lang so browsers and assistive technology choose the right pronunciation, quotes, and hyphenation. Set dir at the document or content boundary where direction changes, preserve digit order, and use <bdi> for isolated mixed-direction values when needed. Spatial mirroring and logical CSS properties belong to better-layout.

19. Keep Useful Text Selectable

::selection can carry brand into the reading experience when the selected combination stays legible. Keep text selectable by default. Use user-select: none only on a specific draggable or gesture-driven surface where accidental selection demonstrably interferes with the interaction; never disable selection across the interface or merely because a button label can be highlighted.

Common Mistakes

Review Output Format

Use this format only when the user asks for a standalone typography review. When studio-audit orchestrates the review, provide domain evidence and findings to that skill and let its output format, severity scale, consolidation rules, cap, and verdict take precedence.

Present the standalone review in two parts.

Findings

Group all confirmed findings by principle. Use a markdown table with Severity, Location, Before, After, and Why columns. Never use separate "Before:" / "After:" lines.

• Severity: HIGH makes text unreadable, unavailable, or structurally misleading; MEDIUM harms hierarchy, wrapping, or scanning; LOW is isolated typographic polish.
• Location: cite path/to/file:line. If the artifact has no source files, cite the exact screen and component instead.
• Before / After: show the current typography and an actionable replacement.
• Why: name the violated principle and its effect on readability or hierarchy.

Consolidate a repeated systemic issue into one row and list every affected location. Omit principles with no findings.

Example

Tabular numbers

Line-height and measure

Verification and Verdict

After the findings:

1. Verification: list the exact checks run and their observed results, including wrapping, hierarchy, text resizing, font loading, and dynamic-value stability when applicable. If a check was not run, state what still needs verification.
2. Verdict: Block if any HIGH finding remains, Needs changes if only MEDIUM or LOW findings remain, and Approve only when no actionable findings remain.

When there are no findings, omit the tables, state "No actionable typography findings", report verification, and end with Approve.