stylelint
Stylelint brings CSS and SCSS linting to .NET projects that bundle stylesheets alongside web frontends. Set up repo-local configuration, define clear ownership boundaries, and enforce naming conventions and duplicate-style cleanup without conflicting with other linters.
Stylelint configures CSS and SCSS linting for .NET repositories with frontend stylesheet assets.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-25
Stylelint configures CSS and SCSS linting for .NET repositories with frontend stylesheet assets. Stylelint brings CSS and SCSS linting to .NET projects that bundle stylesheets alongside web frontends. Set up repo-local configuration, define clear ownership boundaries, and enforce naming conventions and duplicate-style cleanup without conflicting with other linters.
Use it when
- Stylelint's `.stylelintrc` configuration file (JSON, YAML, or JS) defines which CSS/SCSS rules to enforce across your codebase.
- Stylelint enforces stylesheet naming conventions and detects duplicate CSS rules through rules like `no-duplicate-selectors`.
Verify before relying
Read SKILL.md below before installing (3 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/stylelint · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I set up stylelint SCSS in a .NET project?
Stylelint brings CSS and SCSS linting to .NET projects. Install stylelint and a config preset via npm (e.g., `npm install --save-dev stylelint stylelint-config-standard`), then create a `.stylelintrc.json` file in your repo root with your rules. For .NET repos with frontend code in `wwwroot` or `ClientApp`, point stylelint at those directories in your lint command: `stylelint "src/**/*.scss"`. Commit the config file so all team members use identical rules.
What is stylelint .stylelintrc configuration and why do I need it?
Stylelint's `.stylelintrc` configuration file (JSON, YAML, or JS) defines which CSS/SCSS rules to enforce across your codebase. It specifies rule severity (error, warning, off), extends shared configs, and ignores paths like generated assets. For .NET projects, a clear `.stylelintrc` prevents duplicate styles, enforces naming conventions, and ensures consistent stylesheet quality without conflicting with other linters in your build pipeline.
How can stylelint detect and help clean up duplicate CSS rules?
Stylelint enforces stylesheet naming conventions and detects duplicate CSS rules through rules like `no-duplicate-selectors` and `declaration-block-no-duplicate-properties`. Enable these in your `.stylelintrc`, then run stylelint on your stylesheets to identify violations. Combined with autofix (`--fix` flag), stylelint can safely resolve many duplicates automatically, reducing stylesheet bloat in your .NET frontend bundles.
How do I integrate stylelint into my CI/build pipeline?
Stylelint integrates into CI by adding a lint command to `package.json` (e.g., `"lint:styles": "stylelint src/**/*.scss"`) and calling it in your build or pre-commit hooks. For .NET repos, invoke this command in your CI workflow (GitHub Actions, Azure Pipelines, etc.) as a validation gate before deployment. This ensures all stylesheets meet your naming and quality standards before reaching production.
What should I do when stylelint reports an unknown rule error?
Stylelint unknown rule errors occur when your `.stylelintrc` references a rule that isn't installed or recognized. Check that all required plugins (e.g., `stylelint-scss` for SCSS rules) are listed in `devDependencies` and properly configured in your config file. Verify rule names match the stylelint documentation for your version. If upgrading stylelint, review the changelog for renamed or removed rules and update your config accordingly.
How do I use stylelint autofix to safely resolve CSS errors?
Stylelint autofix uses the `--fix` flag to automatically correct fixable violations: `stylelint "src/**/*.scss" --fix`. This safely resolves issues like formatting, property order, and some duplicates without manual editing. Always review changes in version control before committing. For .NET projects, integrate autofix into pre-commit hooks or local development workflows, then run full validation in CI to catch any remaining violations.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
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
Do Not Use For
- JavaScript or TypeScript ownership; route that to
eslintorbiome - runtime accessibility, performance, SEO, or header checks;
(truncated - see the full file via the links below)
File tree — 3 files
catalog/Tools/Stylelint/skills/stylelint/SKILL.md
catalog/Tools/Stylelint/skills/stylelint/manifest.json
catalog/Tools/Stylelint/skills/stylelint/references/release-notes.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Set up and configure Stylelint for CSS/SCSS linting in .NET repositories”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Chous adds architectural guardrails to growing frontend codebases in .NET projects by linting folder structure, naming conventions, and file placement against a checked-in policy. It runs as a CLI gate to catch layout drift before it compounds, complementing semantic linters without replacing them. Use it when structure policy matters more than syntax enforcement.
Metalint aggregates multiple frontend linters into a single CLI entrypoint for .NET repositories with Node-based assets. It delegates to ESLint, Stylelint, HTMLHint, and similar tools while keeping their configs explicit and reviewable under `.metalint/`. Use it when your repo already has multiple linters and needs orchestration, not when a single tool like Biome covers your needs.
webhint runs runtime audits against .NET browser-facing sites, catching accessibility, performance, security header, SEO, and PWA issues that static linters miss. Configure a `.hintrc` baseline, point it at your local or deployed URL, and get categorized findings ready for the team to act on.
Biome integrates into .NET repositories to provide combined formatting, linting, and import organization across JavaScript, TypeScript, CSS, JSON, GraphQL, and HTML. The skill handles ownership decisions between Biome and existing tools like ESLint or Prettier, generates configuration, and establishes repeatable commands for CI and local development. It guides migration strategies and validates that your build and test flows remain stable after changes.
htmlhint enforces HTML structure and attribute correctness on static files and built output in .NET repositories. Target rendered HTML in folders like wwwroot/ or dist/ rather than raw server-side templates, keeping validation separate from JavaScript and full-site audits.
sonarjs integrates SonarJS-derived rules into ESLint for .NET repositories shipping JavaScript or TypeScript frontends. It surfaces cognitive complexity limits, bug-prone patterns, and maintainability issues beyond baseline linting, supporting both local developer workflows via eslint-plugin-sonarjs and server-side SonarQube or SonarCloud gates.
More skills eslint (MIT) · complexity (MIT) · stylecop-analyzers (MIT) · modern-csharp (MIT) · eslint (MIT)