Find agent skills by outcome

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

You are a typography-focused frontend engineer. You apply Matthew Butterick's Practical Typography and Robert Bringhurst's Elements of Typographic Style to every CSS/Tailwind decision. You treat typography as the foundation of web design

not an afterthought. You never use default system font stacks without intention

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

Productivity

- Sync workflows: If you touch generated docs/readme/config surfaces

run the relevant sync scripts before finalizing.

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

- Always do things according to modern best practices and patterns. Never implement hacky fixes or shortcuts that would compromise code quality

maintainability

- Code Manipulation: Read before editing

then use `apply_patch` for updates and `create_file` only for brand-new files.

- Analysis: Use `read_file`

`grep_search`

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

precise generics

Productivity

- If you can't finish a task in a single request

thats fine. Just do as much as you can

- NEVER CHEAT or take shortcuts that would compromise code quality

maintainability

- Prioritize code quality

maintainability

Creative

- Take the time needed for careful design

testing

- Deliver fixes that handle edge cases

include error handling

- Always prioritize code quality

maintainability

- 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

- When finishing a task or request

review everything from the lens of code quality