dotnet-stylelint

Name: dotnet-stylelint
Availability: InStock
Author: postpartum-genushyacinthus29

Run Stylelint against CSS/SCSS assets using repo-local configs.

8|Updated Mar 29, 2026

Search Tags:#frontend #css #dotnet #lint #scss #stylelint

Ready to run

npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-stylelint-postpartum-genushyacinthus29

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-stylelint
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-stylelint
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-stylelint-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CSS and stylesheet quality in .NET projects can drift when frontend assets are shipped with server-side code. This Skill provides a dedicated CLI lint gate using Stylelint for CSS, SCSS, and related assets to catch issues early.

Core Features & Use Cases

Govern stylesheet quality by running Stylelint locally within the repository.
Support scope includes repo-local Stylelint configs and frontend folders such as wwwroot, ClientApp, or src.
Use cases include enforcing selectors and property conventions, identifying duplicate styles, and applying design-system rules before merging changes.

Quick Start

Run stylelint against the repository's CSS/SCSS assets using the local config to surface lint results.

Frequently Asked Questions about dotnet-stylelint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce CSS quality in a .NET project with frontend assets?▼

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.

Do I need a local Stylelint config to lint CSS in .NET repositories?▼

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.

What does Stylelint check for in .NET stylesheet assets?▼

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.

Can I lint SCSS files in my .NET repository's ClientApp folder?▼

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.

What is the best way to catch duplicate CSS styles before merging .NET changes?▼

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.

Why does CSS quality drift in .NET projects with frontend assets?▼

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.