New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Stylelint

by managedcode in managedcode/dotnet-skills

Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends.

MITAuto-check passedFrontend & Design

Install Stylelint

skills CLI
$ npx skills add managedcode/dotnet-skills --skill stylelint -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install managedcode/dotnet-skills stylelint --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Tools/Stylelint/skills/stylelint .claude/skills/stylelint && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stylelint
GitHub stars
486
Token cost
~1.7k tokens
SKILL.md length
786 words
Files
3 (incl. references)
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends.

  • Works in 7 steps: Confirm what Stylelint should own → Prefer repo-local installation and… → Start from a known shared config such as… → …
  • : stylelint.config.
  • SKILL.md covers Trigger On, Do Not Use For, Inputs and Workflow, plus 9 more sections
  • Calls rg, npx and npm

What it does

Stylelint is an agent skill from managedcode/dotnet-skills. Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends. USE FOR: stylelint.config., .stylelintrc, CSS or SCSS assets; CSS linting; duplicate style cleanup and naming-convention checks. DO NOT USE FOR: JavaScript or TypeScript lint ownership; runtime accessibility, performance, SEO, or header checks. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `manifest.json` and `references/release-notes.md`). Compatibility notes: Requires a .NET repository with stylesheet assets such as wwwroot/, ClientApp/, src/, or other frontend folders managed with Node tooling.

It sits in Frontend & Design, covering CSS and styling and Linting and formatting. It works with .NET, JavaScript, TypeScript and npm. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • : stylelint.config.
  • Duplicate style cleanup and naming-convention checks
  • TypeScript lint ownership
  • Runtime accessibility

Example prompts

  • “/stylelint”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Requires a .NET repository with stylesheet assets such as `wwwroot/`, `ClientApp/`, `src/`, or other frontend folders managed with Node tooling.

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Confirm what Stylelint should own
  2. Prefer repo-local installation and checked-in config.
  3. Start from a known shared config such as stylelint-config-standard, then add syntax-specific packages only when the repo truly needs them.
  4. Add repeatable scripts to package.json, for example
  5. Keep ignore patterns explicit so build output, vendored assets, and generated CSS do not pollute the signal.
  6. Treat autofix as controlled cleanup
  7. Use Stylelint for semantic CSS and selector policy, not as a replacement for site-level audits.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • rg
    • npx
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires a .NET repository with stylesheet assets such as `wwwroot/`, `ClientApp/`, `src/`, or other frontend folders managed with Node tooling.

    From compatibility in the SKILL.md frontmatter.

Context cost

Stylelint loads about 1.7k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 127 tokens; SKILL.md has 786 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~127
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 786 words, ~1,708 tokens.

Download SKILL.mdSave it as .claude/skills/stylelint/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
stylelint
description
Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends. USE FOR: stylelint.config.*, .stylelintrc*, CSS or SCSS assets; CSS linting; duplicate style cleanup and naming-convention checks. DO NOT USE FOR: JavaScript or TypeScript lint ownership; runtime accessibility, performance, SEO, or header checks. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility
Requires a .NET repository with stylesheet assets such as `wwwroot/`, `ClientApp/`, `src/`, or other frontend folders managed with Node tooling.

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 eslint or biome
  • runtime accessibility, performance, SEO, or header checks; route that to webhint
  • repos that intentionally use only Biome for CSS linting and do not want a separate stylesheet linter

Inputs

  • the nearest AGENTS.md
  • package.json
  • stylelint.config.* or .stylelintrc*
  • the stylesheet file types in scope: CSS, SCSS, Less, embedded styles, or generated output

Workflow

  1. Confirm what Stylelint should own:
    • plain CSS only
    • CSS plus SCSS
    • embedded styles in HTML, Markdown, or framework files
  2. Prefer repo-local installation and checked-in config.
  3. Start from a known shared config such as stylelint-config-standard, then add syntax-specific packages only when the repo truly needs them.
  4. Add repeatable scripts to package.json, for example:
    • stylelint "**/*.{css,scss}"
    • stylelint "**/*.{css,scss}" --fix
  5. Keep ignore patterns explicit so build output, vendored assets, and generated CSS do not pollute the signal.
  6. Treat autofix as controlled cleanup:
    • run on a bounded scope first
    • inspect the diff
    • rerun the frontend build if the repo compiles styles
  7. Use Stylelint for semantic CSS and selector policy, not as a replacement for site-level audits.

Bootstrap When Missing

  1. Detect current state:
    • rg --files -g 'package.json' -g 'stylelint.config.*' -g '.stylelintrc*'
    • rg -n '"stylelint"|"stylelint-config-" --glob 'package.json' .
  2. Prefer a repo-local install:
    • npm install --save-dev stylelint stylelint-config-standard
  3. Add syntax packages only when the repo needs them for SCSS or embedded styles.
  4. Create or refine stylelint.config.js, stylelint.config.mjs, or the existing config format.
  5. Add repeatable commands to AGENTS.md and package.json, then verify with:
    • npx stylelint "**/*.{css,scss}"
    • npx stylelint "**/*.{css,scss}" --fix
  6. Return status: configured if Stylelint is now wired and repeatable, or status: improved if the existing baseline was tightened.
  7. Return status: not_applicable only when another documented tool already owns stylesheet linting and migration is not requested.

Handle Failures

  • Unknown rule usually means the config expects a plugin or a different Stylelint major version.
  • Unknown word on SCSS, Vue, or mixed-content files usually means the repo needs the matching custom syntax package instead of plain CSS parsing.
  • Massive autofix churn usually means generated assets or third-party CSS slipped into the lint target.
  • Design-system rule noise should be handled by tuning the checked-in config, not by skipping the linter entirely.
Show full SKILL.md (373 more words)Show less

Current 17.14 Guidance

  • Stylelint 17.14.1 fixes quiet suppressing report* warnings, unknown-rule diagnostic ranges, invalid background shorthand autofixes when background-size is present, and rule-empty-line-before false positives around shared-line comments. Re-run lint with and without --quiet, and inspect any background autofix diff before accepting it.
  • Stylelint 17.8.0 also added languageOptions.directionality, property-layout-mappings, relative-selector-nesting-notation, and selector-no-deprecated. Re-run the repo baseline after upgrading so any new selector or layout findings are reviewed instead of preserved by default.
  • Use languageOptions.directionality explicitly when the repo styles bidirectional UI or logical properties. That keeps direction-sensitive rules aligned with the intended writing direction rather than inferred behavior.
  • The earlier *syntax deprecation under declaration-property-value-no-unknown still matters on the 17.x line. If the repo still relies on those options, move the compatibility into customSyntax or parser selection instead of extending deprecated rule config.
  • Keep repo ignores focused on generated or vendored assets. Re-check any broad ignore globs after upgrading so they are not masking selector or layout regressions that the new rules now catch.

Official Sources

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

Ralph Loop

  1. Plan: analyze current state, target outcome, constraints, and risks.
  2. Execute one step and produce a concrete delta.
  3. Review the result and capture findings.
  4. Apply fixes in small batches and rerun checks.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with a reason.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current step
  • actions_taken: concrete changes made
  • verification: commands, checks, or review evidence
  • remaining: unresolved items or none

Example Requests

  • "Add Stylelint for the SCSS in this ASP.NET Core app."
  • "Block duplicate selectors and invalid CSS in CI."
  • "Fix the current Stylelint violations without touching generated CSS."

References

  • release-notes.md - Current 17.14.1 and 17.8.0 release changes that matter for repo config, autofix review, rule tuning, and selector/layout validation

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in catalog/Tools/Stylelint/skills/stylelint of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/release-notes.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Stylelint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stylelint compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stylelint this skillmanagedcode/dotnet-skills486—~1.7kAutomated safety check: PassMIT
Vuetify Skilldlogue/vite-vuetify-ts-starter1811 repos~1.9kAutomated safety check: PassMIT
Fallowfallow-rs/fallow-skills129—~8.2kAutomated safety check: PassMIT
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop5.2k—~2.2kAutomated safety check: PassMIT
Prepare Rslint npm Releaseweb-infra-dev/rslint460—~1.5kAutomated safety check: PassMIT
Igniteui Angular LintingIgniteUI/igniteui-angular599—~614Automated safety check: PassCustom licence

Similar skills

  • Vuetify Skilld

    logue/vite-vuetify-ts-starter

    Vue Material Component Framework. An agent skill from logue/vite-vuetify-ts-starter.

    181 GitHub starsUsed in 1 repo~1.9k tokens
    Frontend & DesignAuto-check passed

  • Fallow

    fallow-rs/fallow-skills

    Codebase intelligence for TypeScript and JavaScript. An agent skill from fallow-rs/fallow-skills.

    129 GitHub stars~8.2k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Install Anti-Slop Oxlint Rules

    dmmulroy/anti-slop

    Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.

    5.2k GitHub stars~2.2k tokensUpdated 27 days ago
    DevelopmentAuto-check passed

  • Prepare Rslint npm Release

    web-infra-dev/rslint

    Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata.

    460 GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Igniteui Angular Linting

    IgniteUI/igniteui-angular

    Quick-reference for linting the core Ignite UI for Angular library.

    599 GitHub stars~614 tokensUpdated today
    DevelopmentAuto-check passed

  • Git Hooks

    Prorise-cool/Claude-Code-Multi-Agent

    Central authority on git hook implementations, modern best practices, and tooling for .NET/C, JavaScript/TypeScript, Python, and polyglot repositories.

    305 GitHub stars~3.6k tokensUpdated 21 days ago
    DevelopmentAuto-check: notes

More from managedcode/dotnet-skills

All 81 skills in this repo

  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Stylelint

What does Stylelint do?

Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends. Stylelint is an agent skill from managedcode/dotnet-skills.NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends.

When should I use Stylelint?

Stylelint fits situations like: : stylelint.config; duplicate style cleanup and naming-convention checks; typeScript lint ownership; runtime accessibility.

How do I install Stylelint in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill stylelint -a claude-code`. Or copy the skill folder (catalog/Tools/Stylelint/skills/stylelint in managedcode/dotnet-skills) into .claude/skills/stylelint in your project. Claude Code loads it when a task matches its description.

How do I install Stylelint in Codex?

Run `npx skills add managedcode/dotnet-skills --skill stylelint -a codex`. Or copy the skill folder (catalog/Tools/Stylelint/skills/stylelint in managedcode/dotnet-skills) into .agents/skills/stylelint in your project. Codex loads it when a task matches its description.

Can I use Stylelint in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add managedcode/dotnet-skills --skill stylelint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stylelint, .gemini/skills/stylelint, .github/skills/stylelint and .opencode/skills/stylelint in your project.

What does Stylelint need to run?

Going by SKILL.md and its folder, Stylelint needs the command-line tools its instructions call (rg, npx and npm). Our summary lists: Node.js. Compatibility (from SKILL.md): Requires a .NET repository with stylesheet assets such as `wwwroot/`, `ClientApp/`, `src/`, or other frontend folders managed with Node tooling..

Does Stylelint access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Stylelint safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stylelint use?

Stylelint is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stylelint use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 638 tokens, read only when the agent opens those files.

What are the alternatives to Stylelint?

Skills that share tags, products or a category with Stylelint: Vuetify Skilld (logue/vite-vuetify-ts-starter, 181 stars), Fallow (fallow-rs/fallow-skills, 129 stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.2k stars) and Prepare Rslint npm Release (web-infra-dev/rslint, 460 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stylelint?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/dotnet-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.