Stylelint for Stylesheets in .NET Repositories

Trigger On

• the repo has stylelint.config.*, .stylelintrc*, or CSS and SCSS assets under frontend folders
• the user asks for CSS linting, duplicate style cleanup, naming convention enforcement, or design-system guardrails
• the repo needs a stylesheet gate beyond formatting alone

Workflow

1. Confirm what Stylelint should own:

- plain CSS only - CSS plus SCSS - embedded styles in HTML, Markdown, or framework files

1. Prefer repo-local installation and checked-in config.
2. Start from a known shared config such as stylelint-config-standard, then add syntax-specific packages only when the repo truly needs them.
3. Add repeatable scripts to package.json, for example:

- stylelint "**/*.{css,scss}" - stylelint "**/*.{css,scss}" --fix

1. Keep ignore patterns explicit so build output, vendored assets, and generated CSS do not pollute the signal.
2. Treat autofix as controlled cleanup:

- run on a bounded scope first - inspect the diff - rerun the frontend build if the repo compiles styles

1. Use Stylelint for semantic CSS and selector policy, not as a replacement for site-level audits.

Deliver

• explicit stylesheet lint ownership
• checked-in config and repeatable commands
• clear scope boundaries for CSS, SCSS, and generated assets

Validate

• the lint target matches the repo's real stylesheet sources
• ignores exclude generated or vendored assets
• Stylelint ownership does not conflict with Biome without an explicit plan
• fixes were verified against the repo's stylesheet build flow when one exists

References

Related skills

Related agents