agentleFS
Sign inStart free
qyndexqyndex/claude-init/.claude/skills/typography/SKILL.md

typography

Skill2 starsChanged 5 months agoMITView on GitHub

Use when setting fonts, type scale, headings, body text, or measure. Enforces typographic hierarchy, readable measure, self-hosted fonts, semantic heading levels. Round 9 C.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use graphic-design and ui-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • travisjneumanSkill

    graphic-design

    Professional graphic design principles for digital and print media. Use when creating visual designs, choosing color palettes, typography, layouts, or providing design feedback.

    Also in 3 projects that use this

  • SentrySkill

    ui-design

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use a modular scale defined in tokens.ts:

    line 20
  2. Very specific:

    One <h1> per page: Use semantic levels; don't skip.

    line 43
  3. Distinctive:

    NEVER three families. NEVER Comic Sans, Times New Roman, or system defaults that scream "didn't decide."

    line 55
  4. Very specific:

    Use @fontsource/inter (and similar) packages.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Typography

Mandate

Typography is the load-bearing element of UI design. Get it right and everything else looks better.

Decisions encoded

Type scale

Use a modular scale defined in tokens.ts:

// Perfect fourth (1.250) — versatile, slightly tight
fontSize: {
  xs:   '0.8rem',    // 12.8px
  sm:   '1rem',      // 16px  — base
  base: '1.25rem',   // 20px
  lg:   '1.563rem',  // 25px
  xl:   '1.953rem',  // 31.25px
  '2xl': '2.441rem', // 39px
  '3xl': '3.052rem', // 49px
}

(Or perfect fifth 1.333 for more drama.)

Body

  • 16px minimum. 18px preferred for marketing/editorial.
  • Line-height 1.5+ for body; 1.2-1.3 for headings.
  • Max measure 75ch — max-w-prose in Tailwind. Anything over 80 characters per line is hard to read.

Hierarchy

  • One <h1> per page. Use semantic levels; don't skip.
  • <main>, <nav>, <article>, <aside> landmarks required.
  • Heading levels follow document outline, not visual size.

Font stack

Two families max:

  1. Sans-serif body: Inter / Manrope / Geist / Söhne. Distinctive enough to feel intentional, neutral enough to read.
  2. Monospace: JetBrains Mono / Fira Code / Geist Mono. For code, data, technical UI.

For DISPLAY (h1/h2/hero): use a second sans with more personality, OR a serif (Fraunces, Source Serif), OR a custom display face.

NEVER three families. NEVER Comic Sans, Times New Roman, or system defaults that scream "didn't decide."

Self-hosting

Use @fontsource/inter (and similar) packages. Import in app entry:

import '@fontsource-variable/inter';

Never link to Google Fonts CDN:

  • GDPR liability (Google logs IP)
  • Performance (DNS lookup, CDN connection)
  • Privacy

Hard rules

  • 16px min body
  • One <h1> per page
  • max-w-prose (or 75ch) on every text block
  • Self-hosted fonts only
  • Two font families max
  • Heading levels never skip (h1 → h3 wrong; h1 → h2 → h3 right)

Common pitfalls

  1. Choosing fonts in CSS instead of tokens.ts — drift across the app
  2. Skipping h2 (h1 → h3) — a11y fail
  3. Body text below 16px — accessibility issue
  4. Letter-spacing tweaks per heading — should be in the type scale, not ad-hoc
  5. Fixed pixel sizes — use rem so user preferences scale

References

Done means

  • Type scale defined in tokens.ts
  • Body ≥ 16px / line-height ≥ 1.5
  • Heading hierarchy correct
  • Fonts self-hosted
  • max-w-prose on text blocks

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free