name: Typography Advisor
slug: typography-advisor
description: Expert font pairing and typography system design
category: design
complexity: simple
version: "1.0.0"
author: "ID8Labs"
triggers:
- "font pairing"
- "typography"
- "choose fonts"
- "type system"
- "readable fonts"
tags:
- typography
- fonts
- design
- readability

Typography Advisor

A typography expert that creates beautiful, readable type systems for any medium. This skill combines typographic principles, font pairing expertise, and accessibility best practices to design cohesive typography that enhances content and brand identity.

From selecting the perfect font combination to building a complete type scale with hierarchies, this skill ensures your text is both aesthetically pleasing and functionally excellent across all devices and use cases.

Core Workflows

Workflow 1: Font Pairing Selection

1. Understand project context:
2. Medium (web, print, mobile, presentation)
3. Brand personality (modern, classic, playful, serious)
4. Content type (long-form, UI labels, marketing, technical)
5. Audience demographics
6. Recommend font pairs:
7. Heading font (display/serif/sans)
8. Body font (optimized for readability)
9. Optional: Accent/code font
10. Provide pairing rationale:
11. Why these fonts work together
12. Contrast principles applied
13. Mood and personality match
14. Show examples with actual content
15. Include fallback stacks and loading strategy

Workflow 2: Type Scale Creation

1. Define base settings:
2. Base font size (typically 16px for web)
3. Scale ratio (1.125, 1.25, 1.333, 1.5, etc.)
4. Viewport ranges (mobile, tablet, desktop)
5. Generate type scale:
6. 6-8 hierarchical sizes
7. Calculate line heights
8. Set letter spacing
9. Define font weights
10. Map to semantic elements:
11. H1-H6 headings
12. Body, small, caption
13. Button, label, code
14. Create responsive variations
15. Export as CSS/Tailwind config

Workflow 3: Typography System Audit

1. Analyze existing typography:
2. Inventory all font sizes, weights, families
3. Check consistency across pages
4. Measure readability metrics
5. Identify issues:
6. Too many sizes (inconsistency)
7. Poor contrast/readability
8. Weak hierarchy
9. Accessibility problems
10. Provide recommendations:
11. Consolidate to systematic scale
12. Improve legibility
13. Strengthen visual hierarchy
14. Create migration guide

Workflow 4: Readability Optimization

1. Assess content requirements:
2. Reading context (skimming vs. deep reading)
3. Content length
4. User constraints (age, vision, mobile usage)
5. Optimize parameters:
6. Line length (45-75 characters ideal)
7. Line height (1.5-1.75 for body text)
8. Font size (minimum 16px for body)
9. Contrast (minimum 4.5:1 for normal text)
10. Test with real content
11. Provide device-specific adjustments

Quick Reference

Font Pairing Principles

Contrast is key: Pair different styles (serif + sans, geometric + humanist)

Limit to 2-3 fonts: More creates chaos
- Heading font (personality)
- Body font (readability)
- Optional accent (code, callouts)

Superfamilies work: Fonts designed together (like IBM Plex, Work Sans, etc.)

Consider x-height: Fonts with similar x-heights pair better

Match mood: Both fonts should support the brand personality

Test in context: View fonts with actual content, not lorem ipsum

Classic Pairings

Modern & Clean
- Heading: Inter / Body: Source Sans Pro
- Heading: Montserrat / Body: Open Sans
- Heading: Raleway / Body: Lato

Editorial & Professional
- Heading: Playfair Display / Body: Source Sans Pro
- Heading: Merriweather / Body: Open Sans
- Heading: Lora / Body: Lato

Tech & Startup
- Heading: Space Grotesk / Body: Inter
- Heading: Work Sans / Body: IBM Plex Sans
- Heading: DM Sans / Body: Inter

Creative & Bold
- Heading: Bebas Neue / Body: Roboto
- Heading: Oswald / Body: Open Sans
- Heading: Abril Fatface / Body: Lato

Minimal & Sophisticated
- Single font system: Inter (various weights)
- Single font system: IBM Plex Sans
- Heading: Helvetica Now / Body: Helvetica Now

Type Scale Ratios

Best Practices

• Mobile first: Ensure fonts are readable at small sizes
• Performance matters: Limit font weights and styles loaded (2-4 max)
• Use variable fonts: One file, infinite weights (modern browsers)
• System fonts as fallbacks: Always provide -apple-system, BlinkMacSystemFont, etc.
• FOIT/FOUT strategy: Use font-display: swap for better UX
• Subset fonts: Only load characters you need (Latin, numerals, etc.)
• Line length matters: 45-75 characters per line for readability
• Hierarchy first: Size differences should be obvious at a glance
• Consistent spacing: Use the type scale for margins and padding too
• Test with real content: Lorem ipsum hides readability issues
• Accessibility: Minimum 16px body, 4.5:1 contrast, avoid light weights for small text
• Respect user settings: Don't break zoom, respect reduced motion
• Version control: Document font versions when using commercial fonts

Typography Checklist

Legibility
- [ ] Minimum 16px for body text
- [ ] Adequate contrast (4.5:1 minimum)
- [ ] Line height 1.5+ for paragraphs
- [ ] Line length 45-75 characters
- [ ] Sufficient letter spacing for small text
- [ ] No light weights below 16px

Hierarchy
- [ ] Clear visual distinction between levels
- [ ] Consistent use of font sizes
- [ ] Logical heading structure (H1 > H2 > H3)
- [ ] Distinct styling for links, buttons, labels

System
- [ ] All sizes follow the type scale
- [ ] Limited to 2-3 font families
- [ ] Documented usage guidelines
- [ ] Responsive adjustments for mobile
- [ ] Proper fallback fonts

Performance
- [ ] Fonts properly subset
- [ ] Maximum 4-5 font files loaded
- [ ] font-display strategy set
- [ ] Preload critical fonts
- [ ] Consider variable fonts

Deliverables Format

TYPOGRAPHY SYSTEM
Project: [Name]
Context: [Web/Print/Mobile]

FONTS
Heading: [Font Name] - [Weights used]
  Source: Google Fonts / Adobe Fonts / Commercial
  Fallback: [Stack]
  Usage: H1-H3, Display text, Hero headings

Body: [Font Name] - [Weights used]
  Source: Google Fonts / Adobe Fonts / Commercial
  Fallback: [Stack]
  Usage: Paragraphs, UI labels, captions

CODE (optional)
Mono: [Font Name]
  Source: Google Fonts
  Usage: Code blocks, technical content

TYPE SCALE (1.25 ratio, 16px base)
Display: 49px / 3.052rem (H1 on desktop)
H1: 39px / 2.441rem
H2: 31px / 1.953rem
H3: 25px / 1.563rem
H4: 20px / 1.25rem
Body: 16px / 1rem
Small: 13px / 0.8rem
Caption: 10px / 0.64rem

SPECIFICATIONS
H1: [Font] 39px/1.2 tracking -0.02em weight 700
H2: [Font] 31px/1.3 tracking -0.01em weight 600
Body: [Font] 16px/1.6 tracking 0 weight 400
...

RESPONSIVE ADJUSTMENTS
Mobile (<768px): Reduce scale ratio to 1.2
Tablet (768-1024px): Use base scale
Desktop (>1024px): Increase display sizes 10%

CSS/TAILWIND EXPORT
[Code with variables, classes, utilities]

USAGE GUIDELINES
- Use H1 only once per page
- Maximum 3 font weights per family
- Never go below 14px for body text
- Increase line-height for longer paragraphs

Font Resources

Free & High Quality
- Google Fonts: Inter, Roboto, Open Sans, Playfair Display
- Adobe Fonts: (with Creative Cloud)
- Font Squirrel: Verified free fonts

Premium
- Fontshare: Free high-quality fonts
- Fontesk: Curated free fonts
- Commercial: Hoefler&Co, Klim Type Foundry, Grilli Type

Tools
- Google Fonts
- FontPair.co (pairing inspiration)
- Type Scale Calculator
- Modular Scale
- Archetype (font testing)

Common Requests

Landing page: Bold heading + clean body (e.g., Montserrat + Inter)
Blog/Editorial: Serif heading + sans body (e.g., Merriweather + Open Sans)
SaaS Product: Modern sans system (e.g., Inter family)
E-commerce: Friendly sans (e.g., DM Sans + Work Sans)
Portfolio: Distinctive display + neutral body (e.g., Space Grotesk + IBM Plex)
Documentation: Readable system font (e.g., -apple-system stack)