When generating CSS
Tailwind classes
Explore
125,085 skills indexed with the new KISS metadata standard.
Tailwind classes
not an afterthought. You never use default system font stacks without intention
spacing
---
the tool will stop tracking the command after that duration and return the output collected so far.
run the relevant sync scripts before finalizing.
also run the repository's package-validation scripts if they exist (for example package-json lint
`grep_search`
then use `apply_patch` for updates and `create_file` only for brand-new files.
thats fine. Just do as much as you can
maintainability
maintainability
precise generics
maintainability
supported patterns and best practices; propose migrations when older or deprecated approaches are encountered.
checking for type errors
include error handling
maintainability
review everything from the lens of code quality
you should redirect the command to a file and read it using proper tools. Put these files in the `temp/` directory. This folder is automatically cleared between prompts
fail gracefully. Do not crash the linter process.
testable utility functions.
keep that authored metadata static and explicit.
check whether the standard library