- Use built-in TypeScript utility types first
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
Explore
125,021 skills indexed with the new KISS metadata standard.
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
`walkRules`
`messages`
repeated reparsing of selector/value strings
coverage outputs
think beyond only unit tests.
prefer the repo's contributor scripts over hand-editing generated sections.
peer dependency ranges
many plugin repos also enforce:
configs
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
type-safe utilities and rules.
value
roots