- Break down PostCSS traversal logic into small
testable utility functions.
Explore
122,573 skills indexed with the new KISS metadata standard.
testable utility functions.
fail gracefully. Do not crash the linter process.
check whether the standard library
scope it carefully and document the expected `customSyntax` or file context.
report only.
comments
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
`walkRules`
repeated reparsing of selector/value strings
coverage outputs
think beyond only unit tests.
peer dependency ranges
many plugin repos also enforce:
sync/validation flows may include:
that often includes:
check whether there is already a matching script
entrypoints
while `eslint.config.mjs` still governs the repository's own JS/TS/Markdown/YAML linting.
existing repository helpers
Quality Gates
hard truth. If I propose a rule that is impossible to implement performantly
but performant
direct `stylelint.lint(...)` integration tests
focusing on compiler APIs