design-typography
Skill9 starsChanged 2 months agoMITView on GitHub
Use when choosing fonts, defining or repairing a type scale, loading webfonts, or fixing text wrapping, truncation, numeric alignment, mixed-direction text, “tipografi”, “font apa”, “teks kepotong”, or “heading berantakan”.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/design-system-enforcer.mdcCursor rule
- frontend-expertSkill
- accessibilitySkill
- anti-slop-codeSkill
- anti-slop-designSkill
- app-shellSkill
- architectureSkill
- componentsSkill
- content-designSkill
- data-fetchingSkill
- design-colorSkill
- design-directionSkill
- design-foundationsSkill
- design-surfacesSkill
- design-vocabularySkill
- devtoolsSkill
- engineering-vocabularySkill
- fidelitySkill
- formsSkill
- frontend-expertSkill
- marketingSkill
- monitoringSkill
- motion-inspectionSkill
- motionSkill
- performanceSkill
- polishSkill
- prototypeSkill
- quality-loopSkill
- responsiveSkill
- seoSkill
- skill-authoringSkill
- testingSkill
- tokensSkill
- webglSkill
The file
Files
Design Typography
Overview
Typography is a role system verified with real content, not a fashionable font choice. Preserve project fonts first; change them only when the task requires it.
When to use
- Font selection, type roles, scales, hierarchy, or webfont loading
- Poor wrapping, truncation, measure, line-height, or numeric jitter
- Variable fonts, OpenType, localization, language, or bidi rendering
When to skip
- Copy meaning or tone only →
content-design - Heading semantics only →
accessibility - Palette or surface styling only
MUST
| Rule | Detail |
| Recon first | Inspect project fonts, tokens, content roles, languages, and rendered lengths |
| Role-based system | Use semantic roles; do not scatter unrelated sizes and weights |
| Content safety | Meaningful truncated text remains reachable |
| Language-aware | Set language/direction boundaries and test text expansion |
| Evidence labels | Numeric recipes are recommendations unless a standard/project owns them |
| Rendered proof | Verify realistic content at supported widths and zoom |
Workflow
- Inventory — font files, fallbacks, tokens, roles, languages, and failure cases.
- Choose — keep the system or propose alternatives with licensing/loading tradeoffs.
- Systematize — map roles to a restrained scale, weights, leading, measure, and features.
- Harden — wrapping, long IDs, truncation recovery, numerics, fallback and bidi.
- Verify — rendered content, loading behavior, 200% zoom, and target breakpoints.
Boundaries
- May decide: role names and closest project-token mapping.
- Must not: replace brand fonts from taste, infer semantics from visual size, or hide essential text permanently.
Checklist
- Project font and role inventory completed
- Scale, measure, wrapping, truncation, and numerics checked as relevant
- Language, fallback, loading, and zoom checked
- Recommendations distinguished from standards
Depth
Full guide: references/design-typography.md.
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.