What it does
Reads existing site copy, imagery, and current type choices to infer the intended tone (playful, corporate, editorial, technical), then cross-references the theme's available font library or common pairing conventions to propose 2-3 heading/body combinations with a short rationale for each. Leaves the final choice and application to the user rather than auto-swapping fonts.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/typography-pairing-suggester/ (or ~/.claude/skills/typography-pairing-suggester/ for all projects)
GitHub Copilot (VS Code)
.github/skills/typography-pairing-suggester/
OpenAI Codex
.codex/skills/typography-pairing-suggester/
Cursor
.cursor/skills/typography-pairing-suggester/ (or ~/.cursor/skills/typography-pairing-suggester/ globally)
Compatibility
Any WordPress site. Applying a chosen pairing depends on the theme's font management, typically theme.json font families on block themes.
The complete SKILL.md for this skill:
---
name: typography-pairing-suggester
description: Use when a user wants font pairing suggestions, mentions their site's typography feeling off-brand or generic, or asks what fonts would suit their site's tone.
---
# Typography Pairing Suggester
## When to use
The user wants font pairing recommendations for headings and body text that actually match their site's existing tone, rather than a generic "popular pairings" list.
## Procedure
1. Read a sample of existing site copy, imagery, and layout to infer the intended tone: playful, corporate, editorial, technical, and so on.
2. Check the theme's currently available font library or font management system (theme.json font families, or an installed font plugin).
3. Propose 2-3 heading/body pairings that fit the inferred tone, prioritizing fonts already available in the theme's library before suggesting new additions.
4. For each pairing, give a one-line rationale (why this heading font reads as the tone identified, why this body font stays readable at paragraph length).
5. Flag any pairing that would require adding a new font source, and note the licensing or loading tradeoff (extra font file, potential load time impact).
6. Leave the actual swap for the user to approve rather than applying a new font pairing automatically.
## Guardrails
- Don't recommend a body font with poor readability at small sizes just because it matches the heading font's style.
- Check that any newly suggested font is actually available to load (theme library, Google Fonts, or already installed) before recommending it.