- If the template uses additional static docs metadata (for example `description` / `recommended` flags used by sync scripts)
keep that authored metadata static and explicit.
Explore
121,500 skills indexed with the new KISS metadata standard.
keep that authored metadata static and explicit.
testable utility functions.
docs
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