- **Performance First:** Stylelint rules run on every save and often across large generated stylesheets. Avoid repeated whole-root rescans
repeated reparsing of selector/value strings
Explore
126,937 skills indexed with the new KISS metadata standard.
repeated reparsing of selector/value strings
`walkRules`
coverage outputs
prefer the repo's contributor scripts over hand-editing generated sections.
peer dependency ranges
think beyond only unit tests.
many plugin repos also enforce:
sync/validation flows may include:
configs
that often includes:
entrypoints
Quality Gates
check whether there is already a matching script
existing repository helpers
while `eslint.config.mjs` still governs the repository's own JS/TS/Markdown/YAML linting.
but performant
hard truth. If I propose a rule that is impossible to implement performantly
focusing on compiler APIs
direct `stylelint.lint(...)` integration tests
type-safe utilities and rules.
value
roots
custom rules
Goal