Coding & Debugging
PromptBeginner5 minmarkdown
- Always prioritize code quality
maintainability
0
Explore
Find agent skills by outcome
143,125 skills indexed with the new KISS metadata standard.
Showing 24 of 143,125
Coding & Debugging
PromptBeginner5 minmarkdown
- When finishing a task or request
review everything from the lens of code quality
0
Productivity
PromptBeginner5 minmarkdown
- If you are getting truncated or large output from any command
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
0
General
PromptBeginner5 minmarkdown
- **Error Handling:** When parsing weird syntax
fail gracefully. Do not crash the linter process.
0
General
PromptBeginner5 minmarkdown
- Break down PostCSS traversal logic into small
testable utility functions.
0
Data
PromptBeginner5 minmarkdown
- **Template-aware changes:** When changing rule metadata
docs
0
Data
PromptBeginner5 minmarkdown
- If the template uses additional static docs metadata (for example `description` / `recommended` flags used by sync scripts)
keep that authored metadata static and explicit.
0
General
PromptBeginner5 minmarkdown
- **Custom Syntax Awareness:** When a rule depends on syntax that does not exist in plain CSS
scope it carefully and document the expected `customSyntax` or file context.
0
General
PromptBeginner5 minmarkdown
- **Utility Usage:** Before writing a helper function
check whether the standard library
0
General
PromptBeginner5 minmarkdown
3. Edge cases (nested rules
comments
0
General
PromptBeginner5 minmarkdown
- **Fixers:** Only mark a rule as `meta.fixable = true` when the fix is deterministic and safe across supported syntaxes. If a fix is risky
report only.
4
General
PromptBeginner5 minmarkdown
- Use built-in TypeScript utility types first
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
0
Data
PromptBeginner5 minmarkdown
- **Metadata:** Every rule must expose a static `ruleName`
`messages`
0
Business
PromptBeginner5 minmarkdown
- **Step-by-Step:** When designing a Stylelint rule
first describe the PostCSS traversal strategy
0
General
PromptBeginner5 minmarkdown
- **Performance First:** Stylelint rules run on every save and often across large generated stylesheets. Avoid repeated whole-root rescans
repeated reparsing of selector/value strings
0
General
PromptBeginner5 minmarkdown
- **AST Traversal:** Use the narrowest viable PostCSS walk (`walkDecls`
`walkRules`
0
General
PromptBeginner5 minmarkdown
- `dist/`
coverage outputs
0
Data
PromptBeginner5 minmarkdown
- If the repository uses all-contributors or similar generated contributor metadata
prefer the repo's contributor scripts over hand-editing generated sections.
0
General
PromptBeginner5 minmarkdown
- If the repository syncs Node version files
peer dependency ranges
0
General
PromptBeginner5 minmarkdown
- If your change touches one of those surfaces
think beyond only unit tests.
0
General
PromptBeginner5 minmarkdown
- Beyond ESLint and TypeScript
many plugin repos also enforce:
3
General
PromptBeginner5 minmarkdown
- In repositories like this one
sync/validation flows may include:
0
Data
PromptBeginner5 minmarkdown
- If rule metadata
configs
0
General
PromptBeginner5 minmarkdown
- In repositories like this template
that often includes:
0