- **Template-aware changes:** When changing rule metadata
docs
Explore
138,327 skills indexed with the new KISS metadata standard.
docs
testable utility functions.
keep that authored metadata static and explicit.
scope it carefully and document the expected `customSyntax` or file context.
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