- **Utility Usage:** Before writing a helper function
check whether the standard library
Explore
129,016 skills indexed with the new KISS metadata standard.
check whether the standard library
comments
`messages`
report only.
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
`walkRules`
repeated reparsing of selector/value strings
peer dependency ranges
coverage outputs
prefer the repo's contributor scripts over hand-editing generated sections.
sync/validation flows may include:
think beyond only unit tests.
many plugin repos also enforce:
that often includes:
configs
entrypoints
existing repository helpers
check whether there is already a matching script
Quality Gates
hard truth. If I propose a rule that is impossible to implement performantly
while `eslint.config.mjs` still governs the repository's own JS/TS/Markdown/YAML linting.
but performant
type-safe utilities and rules.
direct `stylelint.lint(...)` integration tests