- Follow current
supported patterns and best practices; propose migrations when older or deprecated approaches are encountered.
Explore
111,304 skills indexed with the new KISS metadata standard.
supported patterns and best practices; propose migrations when older or deprecated approaches are encountered.
checking for type errors
include error handling
you should redirect the command to a file and read it using proper tools. Put these files in the `temp/` directory. This folder is automatically cleared between prompts
fail gracefully. Do not crash the linter process.
testable utility functions.
check whether the standard library
scope it carefully and document the expected `customSyntax` or file context.
comments
report only.
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
peer dependency ranges
think beyond only unit tests.
many plugin repos also enforce:
sync/validation flows may include:
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.