stuffbucket UI Typography Rules
Attribution
These rules are distilled from Matthew Butterick's Practical Typography (https://practicaltypography.com). If you find this skill valuable, consider supporting his work directly.
Mode of Operation
These are permanent rules — not trends, not opinions. They come from centuries of typographic practice, validated by how the human eye reads.
ENFORCEMENT (default): When generating ANY UI with visible text, apply every rule automatically. Use correct HTML entities, proper CSS. Do not ask permission. Do not explain. Just produce correct typography.
AUDIT: When reviewing existing code or design, identify violations and provide before/after fixes.
Reference files (read when generating CSS or looking up entities):
references/css-templates.md— Full CSS baseline template, responsive patterns, OpenType featuresreferences/html-entities.md— Complete entity table with all characters and codes
Characters
Quotes and Apostrophes — Always Curly
Straight quotes are typewriter artifacts. Use “ ” for double, ‘ ’ for single.
Apostrophes always point down — identical to closing single quote ’. Smart-quote engines
wrongly insert opening quotes before decade abbreviations ('70s) and word-initial contractions
('n'). Fix with explicit ’.
The <q> tag auto-applies curly quotes when <html lang="en"> is set.
JSX/React Implementation Warning
Unicode escape sequences (\u2019, \u201C, etc.) do NOT work in JSX text content. They render as literal characters.
What works (pick one):
Actual UTF-8 characters (preferred): Paste the real character directly into the source file.
JSX expression with string literal: Wrap in curly braces so the JS engine interprets the escape.
<p>Don{'\u2019'}t do this</p>HTML entity (HTML files only): Use
’— does NOT work in JSX/React.
In JavaScript data arrays and string literals, \u2019 works correctly because the JS engine processes the escape. The bug only affects JSX text content between tags.
Dashes and Hyphens — Three Distinct Characters
| Character | HTML | Use |
|---|---|---|
| - (hyphen) | - |
Compound words (cost-effective), line breaks |
| -- (en dash) | – |
Ranges (1--10), connections (Sarbanes--Oxley Act) |
| --- (em dash) | — |
Sentence breaks---like this |
Never approximate with -- or ---. Em dash typically flush; add   if crushed.
Ellipses — One Character
Use …, not three periods. Spaces before and after; use on the text-adjacent side.
Math and Measurement
Use × for multiplication, − for subtraction. Foot and inch marks are the ONE exception to curly quotes — must be STRAIGHT: ' for foot, " for inch.
Trademark and Copyright
Use real symbols: © ™ ®, never (c) (TM) (R). "Copyright (c)" is redundant — word OR symbol, not both.
Accented Characters
Proper names: accents are MANDATORY (Francois Truffaut, Placido Domingo).
Other Punctuation
- Exclamation points: Budget ONE per long document. Never multiple in a row.
- Ampersands: Correct in proper names only. Write "and" in body text.
Spacing
One Space After Punctuation — Always
Exactly one space after any punctuation. Never two.
Nonbreaking Spaces
prevents line break. Use before numeric refs (§ 42), after copyright (© 2025), after honorifics (Dr. Smith).
Text Formatting
Bold and Italic
Bold OR italic. Mutually exclusive. Never combine. Use as little as possible. Sans serif: bold only — italic sans barely stands out. Never bold entire paragraphs.
Underlining — Never
Never underline in a document or UI. For web links, use subtle styling: text-decoration-thickness: 1px; text-underline-offset: 2px.
All Caps — Less Than One Line, Always Letterspaced
ALWAYS add 5-12% letterspacing. ALWAYS ensure kerning is on. NEVER capitalize whole paragraphs. letter-spacing: 0.06em in CSS.
Small Caps — Real Only
Never fake (scaled-down regular caps). Use font-variant-caps: small-caps with fonts that have real small caps.
Point Size
Print: 10-12pt. Web: 15-25px. Use clamp() for fluid web sizing.
Kerning — Always On
No exceptions. font-feature-settings: "kern" 1; text-rendering: optimizeLegibility;
Font Selection
- No goofy fonts in professional work
- No monospaced for body text — code only
- Max 2 fonts. Each gets a consistent role.
Page Layout
Body Text First
Set body text BEFORE anything else. Four decisions determine everything: font, point size, line spacing, line length.
Line Length — 45-90 Characters
The number one readability factor designers get wrong. CSS: max-width: 65ch on text containers.
Line Spacing — 120-145% of Point Size
line-height: 1.2 to 1.45.
Text Alignment
Left-align for web (default). Justified requires hyphens: auto. Centered: sparingly, only for short titles.
Paragraph Separation — Indent OR Space, Never Both
First-line indent: text-indent: 1.5em. Space between: margin-bottom: 0.75em.
Headings — Max 3 Levels
- Do not all-caps headings (unless very short + letterspaced)
- Do not underline headings
- Emphasize with space above and below
- Use bold, not italic
- Smallest point-size increment needed
hyphens: noneon headings- Space above > space below
Tables — Remove Borders, Add Padding
Data creates an implied grid. Keep only thin rule under header row. padding: 0.5em 1em. Tabular figures for numeric columns. Right-align numbers.
Responsive Web Typography
The rules do not change with screen size. Same line length, line spacing, hierarchy.
- Scale
font-sizeand containerwidthtogether - Always
max-widthon text containers — never edge-to-edge text clamp()for fluid scaling:font-size: clamp(16px, 2.5vw, 20px)- Mobile minimum:
padding: 0 1remon text containers
Maxims of Page Layout
- Body text first — its 4 properties determine everything
- Foreground vs background — do not let chrome upstage body text
- Smallest visible increments — half-points matter
- When in doubt, try both — make samples, do not theorize
- Consistency — same things look the same
- Relate new to existing — each element constrains the next
- Keep it simple — 3 colors and 5 fonts? Think again
- Imitate what you like — emulate good typography from the wild