General
PromptBeginner5 minmarkdown
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
0
Explore
Find agent skills by outcome
131,359 skills indexed with the new KISS metadata standard.
Showing 24 of 131,359Categories: Creative, Education, Cursor-rules, General, Coding & Debugging, Data
Creative
PromptBeginner5 minmarkdown
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)
0
General
PromptBeginner5 minmarkdown
When generating CSS
Tailwind classes
0
Coding & Debugging
PromptBeginner5 minmarkdown
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
0
General
PromptBeginner5 minmarkdown
description: Generate production-grade web typography CSS with correct sizing
spacing
0
General
PromptBeginner5 minmarkdown
Web Typography
---
0
General
PromptBeginner5 minmarkdown
- **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.
0
General
PromptBeginner5 minmarkdown
- **Package validation:** If exports or public types change
also run the repository's package-validation scripts if they exist (for example package-json lint
0
General
PromptBeginner5 minmarkdown
- **Analysis:** Use `read_file`
`grep_search`
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Code Manipulation:** Read before editing
then use `apply_patch` for updates and `create_file` only for brand-new files.
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Always do things according to modern best practices and patterns. Never implement hacky fixes or shortcuts that would compromise code quality
maintainability
0
Coding & Debugging
PromptBeginner5 minmarkdown
- NEVER CHEAT or take shortcuts that would compromise code quality
maintainability
0
General
PromptBeginner5 minmarkdown
- Avoid `any` type; use `unknown` with type guards
precise generics
0
Creative
PromptBeginner5 minmarkdown
- Take the time needed for careful design
testing
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Prioritize code quality
maintainability
0
General
PromptBeginner5 minmarkdown
- Follow current
supported patterns and best practices; propose migrations when older or deprecated approaches are encountered.
0
General
PromptBeginner5 minmarkdown
- Sometimes you may need to take other steps that aren't explicitly requests (running tests
checking for type errors
0
General
PromptBeginner5 minmarkdown
- Deliver fixes that handle edge cases
include error handling
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Always prioritize code quality
maintainability
0
Coding & Debugging
PromptBeginner5 minmarkdown
- When finishing a task or request
review everything from the lens of code quality
0
General
PromptBeginner5 minmarkdown
- **Error Handling:** When parsing weird syntax
fail gracefully. Do not crash the linter process.
0
General
PromptBeginner5 minmarkdown
- Break down PostCSS traversal logic into small
testable utility functions.
0
Data
PromptBeginner5 minmarkdown
- If the template uses additional static docs metadata (for example `description` / `recommended` flags used by sync scripts)
keep that authored metadata static and explicit.
0
General
PromptBeginner5 minmarkdown
- **Utility Usage:** Before writing a helper function
check whether the standard library
0