Find agent skills by outcome

2. Communication — clear

confident

- After I answer each question

give a brief 1-line reaction (like a real interviewer would — neutral

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

`oldstyle-nums` for prose

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)

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

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

- NEVER CHEAT or take shortcuts that would compromise code quality

maintainability

- Prioritize code quality

maintainability

Creative

- Take the time needed for careful design

testing

- Always prioritize code quality

maintainability

- When finishing a task or request

review everything from the lens of code quality

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

keep that authored metadata static and explicit.

- Template-aware changes: When changing rule metadata

docs

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

`messages`

Business

- Step-by-Step: When designing a Stylelint rule

first describe the PostCSS traversal strategy

- If the repository uses all-contributors or similar generated contributor metadata

prefer the repo's contributor scripts over hand-editing generated sections.

- If rule metadata

configs

- Modern TypeScript: TypeScript v5.9+

focusing on compiler APIs

- Code Manipulation: Read before editing

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

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

maintainability

- NEVER CHEAT or take shortcuts that would compromise code quality

maintainability

- Prioritize code quality

maintainability

Creative

- Take the time needed for careful design

testing