typography
Skill2 starsChanged 3 months agoMITView on GitHub
Print-quality typography enforcement for English text. Prevents widows, orphans, and hanging short words (articles, prepositions, conjunctions, dashes) at line ends. Rewrites HTML text nodes to insert ties. Also serves as the canonical short-word list used by /build and /audit.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- AmeerBashaK/claude-skillstheir own version, first seen Nov 16, 2026
- fracazo/design-systemtheir own version, first seen Nov 8, 2026
- soilmass/motion-design-agenttheir own version, first seen Nov 8, 2026
- heydavidf/typographytheir own version, first seen Nov 1, 2026
- Above-the-Fold-Studio/designmd-skillstheir own version, first seen Nov 1, 2026
- ArnavPuri/designskillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use graphic-design and ui-design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
travisjneumanSkillgraphic-design
Professional graphic design principles for digital and print media. Use when creating visual designs, choosing color palettes, typography, layouts, or providing design feedback.
Also in 3 projects that use this
SentrySkillui-design
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- glebis/claude-skills★ 414same name
- danium/practicaltypography★ 29same name
- ArnavPuri/designskills★ 17same name
- soilmass/motion-design-agent★ 7same name
- fracazo/design-system★ 4same name
- AntJanus/skillbox★ 2same name
- qyndex/claude-init★ 2same name
- HugoLopes45/design-skills★ 1same name
- VectorLabAU/skills★ 1same name
- Above-the-Fold-Studio/designmd-skills★ 0same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 7 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
After /build writes a new section — /build calls this automatically as its pass 4b.
- Very specific: line 17
After any copy edit in inbox/texts/ that triggered a rebuild of a section.
- Very specific: line 19
Before /audit as a safety pass.
- Very specific: line 68
If a <p> or <blockquote> spans a column break (rare on landing pages, but happens in multi-column footer or blog-style sections), the first …
- Distinctive: line 74
If a file path was provided, load it.
- Distinctive: line 92
Do NOT rewrite text inside:
- Very specific: line 100
Before writing, diff the file.
- Very specific: line 115
If run inside /build, no report — silent success.
- Distinctive: line 123
English only: Do not attempt to guess other languages' rules.
- Distinctive: line 124
Rewrite text nodes only: Never touch attributes, script, style, or verbatim elements.
- Distinctive: line 126
No visual changes beyond typography: Never move elements, never add wrappers, never touch CSS.
- Distinctive: line 130
Do not attempt to detect actual rendered line breaks (would require a headless browser.
- Very specific: line 131
Do not modify the short-word list per project.
- Distinctive: line 132
Do not run on non-English copy.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/typography
Standalone skill. Takes a completed section (or the full site/index.html) and enforces print typography rules on all English text. Callable anytime — before /audit, after copy edits, whenever the source text changed.
Also the single source of truth for the short-word list that /build (pre-save pass) and /audit (post-build check) both reference.
Language scope: English only. Do not run on any other language.
When to use
- After
/buildwrites a new section —/buildcalls this automatically as its pass 4b. - After any copy edit in
inbox/texts/that triggered a rebuild of a section. - Standalone: user says "fix the typography on the hero" or "re-run typography on the whole site".
- Before
/auditas a safety pass.
Requirements
site/index.htmlexists (or a specific section HTML file was provided).- Content is English. If the copy is in another language, refuse and report which language was detected.
The rules
Rule 1 — Hanging short words at line end
A rendered line MUST NOT end on any of these words. Tie the word to the following word using so they wrap together.
Canonical short-word list (English):
# Articles
a, an, the
# Coordinating conjunctions
and, or, but, nor, for, so, yet
# Subordinating conjunctions & connectors
if, as, at, by, in, on, of, to, up, via, with, into, onto, from, than, then, when, where, while, before, after
# Auxiliary and short verbs
is, am, are, was, were, be, do, does, did, has, have, had, can, will, would, could, should
# Pronouns (short)
I, we, he, she, it, you, they, my, our, his, her, its, your, their, this, that
# Negations & quantifiers (short)
no, not, all, anyCase-insensitive matching, but preserve the original case when rewriting.
Rule 2 — Dashes never end a line
-, –, — must attach to the following word: text — word (nbsp before the dash, regular space after). This is opposite direction from Rule 1 — dash pulls the next word up.
Rule 3 — No orphans
Last line of a heading or a paragraph must contain at least 2 words. If the natural break would leave a single word on the last line, tie the last two words together: ... together with us.
Detection heuristic: for each <h1>, <h2>, <h3>, <p>, <li>, take the last 2-3 words and tie the last two with regardless of length. Cheap, prevents 95% of orphans.
Rule 4 — No widows (advisory)
If a <p> or <blockquote> spans a column break (rare on landing pages, but happens in multi-column footer or blog-style sections), the first line on the new column must contain ≥ 2 lines of the paragraph. This is difficult to detect statically — flag rather than fix.
Process
Step 1. Read input.
- If a file path was provided, load it.
- Otherwise load
site/index.htmland every section CSS to know which classes are text vs decorative.
Step 2. Detect language.
Sample ~200 chars from the largest <p> and the first <h1>. If the character set is not predominantly ASCII English, stop and report. Example refusal: Detected language: Russian. This skill runs on English only. Aborting.
Step 3. Walk text nodes.
For each text node inside a semantic text element (<h1>-<h6>, <p>, <li>, <blockquote>, <figcaption>, <button>, <a> if the anchor's text is a full phrase, <label>):
- Tokenize into words + whitespace runs.
- Rule 1 pass. Scan word-by-word. If word W is in the short-word list AND the following whitespace is a regular space AND the next word W+1 exists — replace the space with
. - Rule 2 pass. Scan for standalone
-,–,—surrounded by spaces. Replace the space before the dash with . - Rule 3 pass. Take the last two words of the text node. Ensure they are joined by
, not a regular space.
Step 4. Skip zones.
Do NOT rewrite text inside:
<code>,<pre>,<kbd>,<samp>,<var>— verbatim by contract.<script>,<style>— not text content.- Any element with
class="no-typo"— user escape hatch. - Attributes (
alt=,title=,placeholder=,aria-label=) — these do not line-wrap in visible layout in the same way.
Step 5. Idempotency check.
Before writing, diff the file. Existing from prior passes must not be duplicated (a the — bug). Collapse {2,} to a single .
Step 6. Save + report.
Save the file. Print a compact report:
typography pass — site/index.html
ties inserted: 47
dashes rewritten: 3
orphans prevented: 12
skipped (code/pre): 5 nodes
no-typo opt-outs: 1 nodeIf run inside /build, no report — silent success. If run standalone, always report.
Escape hatch
class="no-typo" on any element skips it entirely. Use for stylized headings where the designer wants specific manual breaks (e.g. <h1 class="no-typo">Ship<br>fast.</h1>).
Rules of behavior
- English only. Do not attempt to guess other languages' rules.
- Rewrite text nodes only. Never touch attributes, script, style, or verbatim elements.
- Idempotent. Running twice produces the same output as running once.
- No visual changes beyond typography. Never move elements, never add wrappers, never touch CSS.
What NOT to do
- Do not attempt to detect actual rendered line breaks (would require a headless browser; too expensive per pass). Use the word-level heuristics defined above.
- Do not modify the short-word list per project. It's the canonical English list. If the user wants a variant, they can override in a project-local
typography-overrides.md(not currently supported — flag as an enhancement request). - Do not run on non-English copy. Refuse.
Next
/audit— will grep for violations (hanging words, unfixed dashes) as part of category A./build— calls this automatically after each section HTML is written.
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.

