Explore
143,247 skills indexed with the new KISS metadata standard.
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.
keep that authored metadata static and explicit.
testable utility functions.
docs
comments
check whether the standard library
scope it carefully and document the expected `customSyntax` or file context.
report only.
`messages`
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
first describe the PostCSS traversal strategy
repeated reparsing of selector/value strings
`walkRules`
prefer the repo's contributor scripts over hand-editing generated sections.
peer dependency ranges
coverage outputs
sync/validation flows may include:
think beyond only unit tests.
many plugin repos also enforce:
that often includes:
configs
entrypoints
Quality Gates