.agents/skills/typeset/SKILL.md
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
npx skillsauth add youranreus/note typesetInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type.
Invoke /impeccable — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /impeccable teach first.
Analyze what's weak or generic about the current type:
Font choices:
Hierarchy:
Sizing & scale:
rem scales for app UIs; fluid clamp() for marketing/content page headings)Readability:
Consistency:
CRITICAL: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting.
Consult the typography reference from the impeccable skill for detailed guidance on scales, pairing, and loading strategies.
Create a systematic plan:
If fonts need replacing:
font-display: swap, metric-matched fallbacks)Build a clear type scale:
rem-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts needclamp(min, preferred, max) for headings and display text. Keep body text fixedmax-width on text containers using ch units (max-width: 65ch)tabular-nums for data tables and numbers that should alignletter-spacing: slightly open for small caps and uppercase, default or tight for large display text--text-body, --text-heading), not value names (--font-16)font-kerning: normal and consider OpenType features where appropriateNEVER:
user-scalable=no)px for font sizes — use rem to respect user settingsRemember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make.
tools
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
development
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
testing
Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"
development
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"