better-typography

Reviews and fixes web typography covering fonts, spacing, wrapping, and accessibility.

2.7k|171|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill better-typography
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: better-typography
Source: https://github.com/compozy/compozy/tree/main/.agents/skills/better-typography
Command: npx skills add https://github.com/compozy/compozy --skill better-typography

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web interfaces often ship with inconsistent font choices, broken heading hierarchy, poor line lengths, and unreadable text wrapping. This Skill provides a systematic set of typography principles and review procedures so text renders legibly, hierarchically, and accessibly across browsers and devices.

Core Features & Use Cases

  • Font Selection and Loading: Guidance on typeface categories, pairing, woff2 formats, variable font axes, and OpenType features like tabular numbers and stylistic sets.
  • Spacing and Sizing Rules: Type scales, heading hierarchy mapping, unitless line-height, letter-spacing by role, and text-box trimming for optical alignment.
  • Wrapping, Truncation, and Accessibility: text-wrap balance/pretty, line-clamp, smart punctuation, iOS input zoom prevention, font smoothing, and RTL/bidi handling.
  • Structured Review Output: A severity-ranked findings table (HIGH/MEDIUM/LOW) with before/after fixes, verification steps, and a Block/Needs changes/Approve verdict.
  • Use Case: A developer asks for a typography review of a React/Tailwind frontend; the Skill inspects components, flags a full-width article column and missing tabular-nums on live prices, and returns actionable fixes expressed in Tailwind utilities.

Quick Start

Review the typography of my frontend components and report findings with severity, location, and fixes.

Frequently Asked Questions about better-typography

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix typography issues in a Tailwind CSS project?

Apply the Skill's principles using Tailwind utilities: text-balance for headings, text-pretty for descriptions, tabular-nums for changing values, and antialiased on the root layout. The included CSS cheat sheet maps every typography declaration to its Tailwind equivalent.

What font format should I use for web projects?

Use woff2, which offers Brotli compression and broad browser support. woff is a fallback only for very old browsers, while ttf and otf are raw desktop formats without web compression and should be avoided on the web.

How do I stop numbers from shifting layout when values change?

Apply font-variant-numeric: tabular-nums (or the tabular-nums Tailwind class) to timers, counters, and prices. This gives every digit equal width so updating values no longer cause layout shift.

Why does iOS Safari zoom in when focusing my input fields?

iOS Safari zooms the page when input text is smaller than 16px. Set inputs to text-base on mobile and sm:text-sm from the small breakpoint up, and avoid the maximum-scale=1 viewport meta which breaks pinch zoom accessibility.

When should I use font-variation-settings instead of font-weight?

Prefer font-weight and other high-level properties because they keep working with non-variable fallback fonts. Reserve font-variation-settings for custom axes like GRAD that have no corresponding CSS property.

What is the ideal line length for body text?

Cap long-form text at roughly 60-75 characters per line. Use max-w-[65ch], or at 16px body size a pixel cap around 560-680px such as Tailwind's max-w-xl or max-w-2xl.