Find agent skills by outcome

- 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

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

- 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

- Take the time needed for careful design

testing

- 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.

- Break down PostCSS traversal logic into small

testable utility functions.

- Custom Syntax Awareness: When a rule depends on syntax that does not exist in plain CSS

scope it carefully and document the expected customSyntax or file context.

- Utility Usage: Before writing a helper function

check whether the standard library

3. Edge cases (nested rules

comments

- Fixers: Only mark a rule as meta.fixable = true when the fix is deterministic and safe across supp...

report only.

- Use built-in TypeScript utility types first

and use installed utility-type libraries only when they clearly improve intent and match repository conventions.

- AST Traversal: Use the narrowest viable PostCSS walk (walkDecls

walkRules

- Performance First: Stylelint rules run on every save and often across large generated stylesheets....

repeated reparsing of selector/value strings

- If the repository syncs Node version files

peer dependency ranges