dotnet-stylelint

You can enforce CSS quality in a .NET project by running Stylelint checks against CSS and SCSS assets. This process catches stylesheet drift early by identifying duplicate styles, selector issues, and property convention violations before merging changes.

Yes, you need a repo-local Stylelint setup with a configuration file and repeatable commands. The Skill requires this local config to run lint checks against your CSS and SCSS files within folders like wwwroot or ClientApp.

Stylelint checks CSS and SCSS assets for selector conventions, property rules, duplicate styles, and design-system rules. It uses your local configuration to surface these lint results and enforce consistent stylesheet quality.

Yes, you can lint SCSS files in frontend folders such as ClientApp, wwwroot, or src. The Skill runs Stylelint against these CSS and SCSS assets using your repository's local configuration.

The best way to catch duplicate CSS styles is to run a local Stylelint gate as part of your workflow. This identifies duplicates, enforces naming conventions, and applies design-system rules to your CSS and SCSS assets before merge.

CSS quality drifts in .NET projects because frontend assets are shipped with server-side code without a dedicated lint gate. Running Stylelint locally provides a dedicated CLI process to catch stylesheet issues early and maintain consistency.