Best Typography Skills for Claude Code (2026)

Default AI-generated UIs tend to ship with system-font defaults and no type scale. typeset is the most-installed skill fixing this at 65,535 installs (skills.sh registry, pbakaus/impeccable).

Key takeaways

• typeset leads with 65,535 installs and 35,911 GitHub stars (skills.sh registry, GitHub).
• brand-guidelines (62,692 installs, 147,832 stars) is Anthropic's own official skill for applying consistent typography and visual identity.
• web-typography (4,555 installs) generates production-ready CSS typography rules and variable-font setups specifically.
• motion-graphics (58,551 installs) covers kinetic typography for animated content, a distinct use case from static UI type.
• design-tokens (3,404 installs) treats type scale as part of a broader token system alongside color and spacing.

Why does AI-generated UI text look generic?

Coding agents default to system fonts and browser-default sizing unless a skill explicitly sets a type scale, line-height and font-pairing strategy. typeset targets this directly - it turns default-looking text into an intentional system matching a project's brand rather than leaving font choice to browser defaults.

What is the best skill for typography in Claude Code?

typeset leads at 65,535 installs and 35,911 stars (skills.sh registry, GitHub). Install it with:

npx skills add pbakaus/impeccable --skill typeset

Strong alternatives: brand-guidelines (62,692 installs) for teams standardizing on Anthropic's own visual identity rules, and web-typography (4,555 installs) for CSS-level type implementation. See the full design skills shortlist.

How do variable fonts change a typography workflow?

Variable fonts let a single font file serve every weight and width a design needs, cutting page-weight versus loading five static font files. web-typography (4,555 installs, skills.sh registry) generates variable-font setup and font-display strategy specifically, which most general design skills skip.

Should typography be part of a design-token system?

Yes, for consistency across a codebase - design-tokens (3,404 installs) treats type scale as a token category alongside color and spacing, so a single source of truth drives both. See the design systems hub for the broader token toolkit.

A complete starter stack

• typeset - intentional type systems from default-looking text
• web-typography - production CSS rules and variable-font setup
• design-tokens - type scale as part of a token system
• brand-guidelines - consistent typography across UI, docs and slides

Common pitfalls

• Leaving font choice to browser defaults instead of setting an explicit type scale early in the build.
• Loading multiple static font-weight files instead of a single variable font, adding unnecessary page weight.
• Treating typography as separate from the design-token system, so type and color drift out of sync over time.

Set a type scale before writing components - retrofitting typography onto finished UI is slower than starting with it.

Common questions