Find agent skills by outcome

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.

- Utility Usage: Before writing a helper function

check whether the standard library

Data

- Template-aware changes: When changing rule metadata

docs

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

3. Edge cases (nested rules

comments

- Fixers: Only mark a rule as `meta.fixable = true` when the fix is deterministic and safe across supported syntaxes. If a fix is risky

report only.

Data

- Metadata: Every rule must expose a static `ruleName`

`messages`

- Use built-in TypeScript utility types first

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

- Performance First: Stylelint rules run on every save and often across large generated stylesheets. Avoid repeated whole-root rescans

repeated reparsing of selector/value strings

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

`walkRules`