Find agent skills by outcome

- NEVER pair two visually similar fonts (e.g.

two geometric sans-serifs)

- MUST use unitless line-height values (1.3-1.45)

never px or em

- Bold not italic for headings. Subtle size increases (1.2-1.5x steps

not 2x jumps)

- Line length drives breakpoints

not the other way around

- Paragraph spacing via margin-bottom equal to one line-height

no first-line indent for web

- font-variant-numeric: tabular-nums on data/number columns

oldstyle-nums for prose

- Use clamp() for fluid sizing: `clamp(1rem

0.9rem + 0.5vw

- NEVER use vw units alone (breaks user zoom

accessibility violation)

- Free quality options: Source Serif

IBM Plex

- NEVER default to Arial

Helvetica

- Prioritize fonts with generous x-height

open counters

- Pair fonts by contrast (serif body + sans heading

or vice versa)

2. Build a type scale. Use 1.2-1.5x ratio steps from the base size. Do not pick arbitrary heading si...

H3 22px

When generating CSS

Tailwind classes

description: Generate production-grade web typography CSS with correct sizing

spacing

Web Typography

- Package validation: If exports or public types change

also run the repository's package-validation scripts if they exist (for example package-json lint

- Stuck / Hung Commands: You can use the timeout setting when using a tool if you suspect it might h...

the tool will stop tracking the command after that duration and return the output collected so far.

- Analysis: Use read_file

grep_search

- Avoid any type; use unknown with type guards

precise generics

- Deliver fixes that handle edge cases

include error handling

- Sometimes you may need to take other steps that aren't explicitly requests (running tests

checking for type errors

- Follow current

supported patterns and best practices; propose migrations when older or deprecated approaches are encountered.

- Error Handling: When parsing weird syntax

fail gracefully. Do not crash the linter process.