- **Template-aware changes:** When changing rule metadata
docs
Explore
130,867 skills indexed with the new KISS metadata standard.
docs
scope it carefully and document the expected `customSyntax` or file context.
comments
report only.
`messages`
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
repeated reparsing of selector/value strings
`walkRules`
coverage outputs
first describe the PostCSS traversal strategy
peer dependency ranges
prefer the repo's contributor scripts over hand-editing generated sections.
think beyond only unit tests.
many plugin repos also enforce:
sync/validation flows may include:
configs
that often includes:
check whether there is already a matching script
entrypoints
Quality Gates
existing repository helpers
while `eslint.config.mjs` still governs the repository's own JS/TS/Markdown/YAML linting.
hard truth. If I propose a rule that is impossible to implement performantly
direct `stylelint.lint(...)` integration tests