3. Edge cases (nested rules
comments
Explore
120,374 skills indexed with the new KISS metadata standard.
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.
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
check whether there is already a matching script
existing repository helpers
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.