agentleFS
ckorhonenckorhonen/claude-skills/skills/practical-typography/SKILL.md

practical-typography

Skill17 starsChanged 4 months agoMITView on GitHub

Professional typography guidance based on Matthew Butterick's Practical Typography. Use when evaluating, critiquing, or improving document formatting, text layout, font choices, punctuation, spacing, or any typography-related decisions for print or web content.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check point size, line spacing, line length against standards

    line 26
  2. Distinctive:

    Verify font quality (avoid Times New Roman, Arial)

    line 27
  3. Distinctive:

    When reviewing or critiquing typography:

    line 41
  4. Distinctive:

    When users want to:

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Practical Typography

Professional typography guidance based on Matthew Butterick's Practical Typography.

Quick Reference

For typography rules and guidelines, read references/key-rules.md.

Core Principles

Typography quality is determined by:

  1. Body text (most important—there's more of it than anything else)
  2. Point size, line spacing, line length, font
  3. Professional fonts over system fonts
  4. Consistency in formatting choices

Common Use Cases

Evaluating Documents

  • Check point size, line spacing, line length against standards
  • Verify font quality (avoid Times New Roman, Arial)
  • Review spacing, punctuation, special characters

Providing Recommendations

  • Suggest professional font alternatives
  • Calculate optimal line spacing (120–145% of point size)
  • Recommend appropriate line length (45–90 characters)

Web vs. Print

  • Print: 10–12pt, exact line spacing
  • Web: 15–25px, CSS line-height with unitless values

Typography Review Checklist

When reviewing or critiquing typography:

  1. Body text fundamentals
    • Point size in range?
    • Line spacing 120–145%?
    • Line length 45–90 characters?
    • Professional font?
  2. Common mistakes
    • Straight quotes instead of curly?
    • Two spaces after sentences?
    • Underlining (non-links)?
    • Times New Roman or Arial?
    • Fake small caps?
    • Multiple hyphens as dash?
  3. Professional polish
    • Proper em/en dashes?
    • Real trademark symbols?
    • Correct apostrophe direction?
    • Consistent paragraph spacing?
    • Appropriate use of emphasis?

Reference Material

All typography rules and standards: references/key-rules.md

This includes:

  • Typography in ten minutes (essential rules)
  • Summary of key rules (comprehensive)
  • Web-specific guidelines
  • Print-specific guidelines
  • Common mistakes to avoid

When to Recommend This Resource

When users want to:

  • Learn professional typography
  • Review the full reference: https://practicaltypography.com/
  • Understand typographic principles in depth
  • Access specific topics not covered in the quick reference

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.