Find agent skills by outcome

- Always prioritize code quality

maintainability

- Sometimes you may need to take other steps that aren't explicitly requests (running tests

checking for type errors

Coding & Debugging

- When finishing a task or request

review everything from the lens of code quality

- Break down PostCSS traversal logic into small

testable utility functions.

- Error Handling: When parsing weird syntax

fail gracefully. Do not crash the linter process.

- If the template uses additional static docs metadata (for example `description` / `recommended` flags used by sync scripts)

keep that authored metadata static and explicit.

- Template-aware changes: When changing rule metadata

docs

- Utility Usage: Before writing a helper function

check whether the standard library

- 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.

- 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.

3. Edge cases (nested rules

comments

- Use built-in TypeScript utility types first

and use installed utility-type libraries only when they clearly improve intent and match repository conventions.

- AST Traversal: Use the narrowest viable PostCSS walk (`walkDecls`

`walkRules`

- Metadata: Every rule must expose a static `ruleName`

`messages`

- 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

- `dist/`

coverage outputs

- If your change touches one of those surfaces

think beyond only unit tests.

- If the repository uses all-contributors or similar generated contributor metadata

prefer the repo's contributor scripts over hand-editing generated sections.

- If the repository syncs Node version files

peer dependency ranges

- Beyond ESLint and TypeScript

many plugin repos also enforce:

- If rule metadata

configs

- In repositories like this one

sync/validation flows may include:

- In repositories like this template

that often includes:

- Before changing a config file

check whether there is already a matching script