General
PromptBeginner5 minmarkdown
- Pair fonts by contrast (serif body + sans heading
or vice versa)
0
Explore
Find agent skills by outcome
121,580 skills indexed with the new KISS metadata standard.
Showing 24 of 121,580Categories: Communication, Data, General, Creative
General
PromptBeginner5 minmarkdown
- Prioritize fonts with generous x-height
open counters
0
General
PromptBeginner5 minmarkdown
- NEVER default to Arial
Helvetica
0
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
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
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
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
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
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
Data
PromptBeginner5 minmarkdown
- **Template-aware changes:** When changing rule metadata
docs
0
General
PromptBeginner5 minmarkdown
- **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.
0
General
PromptBeginner5 minmarkdown
3. Edge cases (nested rules
comments
0
General
PromptBeginner5 minmarkdown
- **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.
0