Find agent skills by outcome

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

`oldstyle-nums` for prose

- NEVER use `vw` units alone (breaks user zoom

accessibility violation)

- Line length drives breakpoints

not the other way around

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

0.9rem + 0.5vw

- Free quality options: Source Serif

IBM Plex

- Pair fonts by contrast (serif body + sans heading

or vice versa)

- Prioritize fonts with generous x-height

open counters

- NEVER default to Arial

Helvetica

2. Build a type scale. Use 1.2-1.5x ratio steps from the base size. Do not pick arbitrary heading sizes. Example at 18px base with 1.25 ratio: body 18px

H3 22px

Creative

1. Body text first. Always start with the body font. Set its size (16-20px for web)

line-height (1.3-1.45 as unitless value)

When generating CSS

Tailwind classes

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

spacing

Web Typography

---

- Stuck / Hung Commands: You can use the timeout setting when using a tool if you suspect it might hang. If you provide a `timeout` parameter

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

- Package validation: If exports or public types change

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

- Analysis: Use `read_file`

`grep_search`

- Avoid `any` type; use `unknown` with type guards

precise generics

Creative

- Take the time needed for careful design

testing

- Follow current

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

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

checking for type errors

- Deliver fixes that handle edge cases

include error handling

- Error Handling: When parsing weird syntax

fail gracefully. Do not crash the linter process.

- Break down PostCSS traversal logic into small

testable utility functions.

Data

- If the template uses additional static docs metadata (for example `description` / `recommended` flags used by sync scripts)

keep that authored metadata static and explicit.