Ux Typography logo

Ux Typography

Organization
Uxcel-Lab
ux-typography

Design or critique a product's typography — typeface selection and pairing, type scale, hierarchy, and readability settings (size, line length, line height, spacing, alignment). Trigger when choosing a typeface or font pairing, setting up a type scale, fixing typographic hierarchy, improving text readability, or reviewing a UI layout for typography issues.

Overview

PublisherUxcel-Lab
Repositoryproduct-skills
Skill nameux-typography
Stars
35
Forks
8
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Uxcel-Lab on GitHub. Read the source before you install it.

Installation

Install the Ux Typography AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Uxcel-Lab/product-skills/tree/main/ux/foundations/typography
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Uxcel-Lab/product-skills.git /tmp/product-skills
mkdir -p .claude/skills
cp -r /tmp/product-skills/ux/foundations/typography .claude/skills/ux-typography
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ux Typography in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ux Typography on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ux Typography is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Typography Skill

How this skill behaves (read first)

This is a generative skill. Typography has two default failure modes: bland (pick one safe font, no real scale or hierarchy) and over-expressive (multiple display faces, many weights/colors/cases stacked → cluttered and illegible). So this skill gates:

  1. Establish brand personality, content types, and medium — these drive the expressive choices worth making.
  2. Apply the always-true core — legibility, a clear scale/hierarchy, and restraint hold for any product.
  3. Make the typeface/pairing/scale choices deliberately — surface them as gated decisions tied to brand, not defaults.

Then hand off to the audits: accessibility (size, contrast, spacing), aesthetics (hierarchy, balance).


Step 0 — Establish context before choosing type

  • Brand personality & expected aesthetics — what impression should it make, and what does the audience expect (a kids' app vs. a banking app demand opposite tone)?
  • Content types — what kinds of text exist (display, headings, body, captions, labels)? This sizes the hierarchy.
  • Medium — long-form reading vs. dense UI vs. marketing — changes the legibility/expressiveness balance.
  • Language direction — LTR vs. RTL (drives default alignment).

State assumptions if proceeding without answers.


The always-apply core (true for any typography)

Readability & legibility (body text)

  • Body ≥ 16px. Start the scale from body size (it occupies the most space), then size up/down.
  • Line length 50–75 characters. Longer is hard to track; too short forces choppy eye movement.
  • Line height ~150% of font size for body; larger sizes/widths need more.
  • Paragraph spacing ≥ 1.5× line spacing (WCAG); separate ideas into digestible blocks.
  • Left-align body text in LTR (right for RTL). Reserve center alignment for short elements (headlines, quotes, CTAs) — it slows reading and hurts users with cognitive/visual impairments.
  • Design for scannability — ~79% of users scan, ~3% read word-by-word; hierarchy + spacing make scanning work.

Hierarchy & restraint

  • Limit to ≤3 typefaces — often one superfamily with good weight/style variety is enough.
  • Build a type scale (size, weight, style) covering the content types; keep levels distinct.
  • Use ≤3 hierarchy instruments (size, weight, style, color, case) per level and 2–3 heading levels; stacking all of them is clutter (a huge, bold, colored, all-caps headline shouts).
  • Emphasis is soft and singular — italics (softest) or bold, not several at once; color in type sparingly.
  • Group with white space & proximity — related text close, unrelated separated.

The context-dependent decisions (surface, don't auto-apply)

Present each with its trade-off and a recommendation tied to Step 0. Stacking display faces, weights, and decoration is the failure mode.

DecisionApply whenAvoid / adapt whenDefault recommendation
Typeface personality / moodA display/character face fits the brand and appears only in headingsUsing an expressive face for body text (kills readability)Character in display, high-legibility for body
One vs. two typefacesA heading/body pairing adds useful contrastA third face, or pairing that lacks clear contrastOne superfamily by default; add a second only with clear contrast + role
Number of weightsA few weights to build hierarchyA weight for every whimThe minimum that makes the scale legible
Type-scale ratioDramatic ratio for marketing/editorial impactDramatic ratio in dense UI (wastes space)Modest ratio for product UI; bolder for marketing
Serif vs. sansMatch medium/brand (serif long-form/editorial trust; sans UI clarity)Choosing by taste against the mediumFit the medium and audience expectation
Decorative touches (drop caps, pull/block quotes)Editorial/long-form layoutsProduct UI, forms, dense screensEditorial only

Always avoid (regardless of context): typographic clichés (Papyrus for "ancient", Comic Sans for "fun"), anachronisms (period-mismatched faces), and appropriateness failures (a casual script on a banking app). Explore beyond the obvious; prioritize fit over novelty.


Validate the result (orchestration)

Hand-offs name each lens by its installable skill name. Invoke one only if that skill is installed; if it isn't, this skill's own core already carries these rules — proceed without it rather than blocking.

After choosing or revising type, hand the result to the audit lenses rather than declaring it done. These are candidate lenses — posture is set by docs/orchestration-policy.md, or route the whole thing through ux-design-review. Here, microcopy is Tier A (auto-run); accessibility and aesthetics are Tier B (offered) — under an existing design system aesthetics is suppressed and accessibility narrows to usage. If the user invoked this skill for one specific thing, respect that scope.

  • ux-accessibility-audit (Tier B — offer; narrow under a design system) — body ≥16px, contrast of text on its background, line length/height and paragraph spacing, alignment, and that hierarchy doesn't rely on color alone.
  • ux-aesthetics-audit (Tier B — offer; suppress under a design system) — typographic hierarchy effectiveness, balance, white space, and whether the type treatment tipped into clutter (>3 instruments, too many faces).
  • ux-microcopy-audit (Tier A) — the words themselves (this skill sets how text looks, not what it says).

If accessibility flags readability or aesthetics flags clutter, return to the core: fewer faces, fewer instruments, a cleaner scale.


Common do/don't patterns

❌ Don't✅ Do
One safe font, no scale or hierarchyA deliberate type scale with 2–3 distinct levels
3+ typefaces / a display face for body≤3 faces; often one superfamily; display only in headings
Big + bold + colored + ALL-CAPS headline≤3 hierarchy instruments per level
Body text < 16pxBody ≥16px, scale built up from there
Full-width lines of text50–75 characters per line
Tight, cramped line spacing~150% line height; paragraph spacing ≥1.5×
Center-aligned body paragraphsLeft-align body (LTR); center only short elements
Papyrus/Comic Sans clichés; anachronistic facesAppropriate, considered faces explored beyond the obvious
Ship without checkingHand off to accessibility + aesthetics

Source lessons (Uxcel)

Frequently asked questions

What does the Ux Typography AI skill do?

Design or critique a product's typography — typeface selection and pairing, type scale, hierarchy, and readability settings (size, line length, line height, spacing, alignment). Trigger when choosing a typeface or font pairing, setting up a type scale, fixing typographic hierarchy, improving text readability, or reviewing a UI layout for typography issues.

Why use Ux Typography on TypingMind?

Because you install it once and use it with any model. Ux Typography is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ux Typography in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Uxcel-Lab/product-skills/tree/main/ux/foundations/typography. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ux Typography?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ux Typography?

As many as you like. As long as a model supports skills, you can use Ux Typography with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ux Typography AI skill free?

Yes. It is published on GitHub by Uxcel-Lab under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇