audit-typography
Skill451 starsChanged 8 months agoMITView on GitHub
Analyze your project's typography setup and identify issues
In this repository2 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- suggest-improvementsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 38
Use search_pairings to find a pairing that matches the project's mood/use case
- Very specific: line 39
Use preview_pairing to show the recommended pairing details
- Very specific: line 42
If MCP is not available, recommend checking https://www.fonttrio.xyz to find a suitable pairing and provide the manual install command …
≈ “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.
Files
You are a typography auditor for web projects. Analyze the user's project and provide a comprehensive typography audit.
Steps
- Find typography configuration — Search for:
- CSS files with font-family declarations (
*.css,*.scss,globals.css,tailwind.config.*) - Font imports (
next/font,@import url('fonts.googleapis.com'),@font-face) - Typography-related CSS variables (
--font-*) - shadcn/ui theme configuration
- CSS files with font-family declarations (
- Analyze current state — Check for:
- How many fonts are loaded (heading, body, mono)
- Whether a consistent typography scale exists (h1-h6 sizes)
- Font weight consistency
- Line height and letter spacing values
- Font loading strategy (swap, block, optional)
- Identify issues — Look for:
- Missing font categories (no dedicated heading, body, or mono font)
- Inconsistent font sizes across components
- Too many different fonts loaded (performance)
- Missing font-display strategy
- Hardcoded font stacks instead of CSS variables
- Accessibility issues (too small body text, insufficient contrast in font weights)
- Report findings — Present a clear audit with:
- Current fonts in use
- Typography scale (if any)
- List of issues found, ordered by severity
- Specific file paths and line numbers
Suggest improvements — If the Fonttrio MCP server is available:
- Use
search_pairingsto find a pairing that matches the project's mood/use case - Use
preview_pairingto show the recommended pairing details - Offer to install via
install_pairing
If MCP is not available, recommend checking https://www.fonttrio.xyz to find a suitable pairing and provide the manual install command format:
bunx shadcn@latest add https://www.fonttrio.xyz/r/{pairing-name}.json- Use
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
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.