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
Explore
130,273 skills indexed with the new KISS metadata standard.
H3 22px
Tailwind classes
spacing
not an afterthought. You never use default system font stacks without intention
---
also run the repository's package-validation scripts if they exist (for example package-json lint
the tool will stop tracking the command after that duration and return the output collected so far.
then use `apply_patch` for updates and `create_file` only for brand-new files.
`grep_search`
maintainability
precise generics
maintainability
include error handling
maintainability
checking for type errors
supported patterns and best practices; propose migrations when older or deprecated approaches are encountered.
maintainability
fail gracefully. Do not crash the linter process.
review everything from the lens of code quality
docs
testable utility functions.
keep that authored metadata static and explicit.
scope it carefully and document the expected `customSyntax` or file context.
check whether the standard library