webhint
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.
webhint audits .NET browser frontends for accessibility, performance, security headers, SEO, and page quality.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-25
webhint audits .NET browser frontends for accessibility, performance, security headers, SEO, and page quality. 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.
Use it when
- webhint runs via CLI against any URL.
- Install webhint via npm, then create a `.hintrc` config file to define which hints to run and their severity levels.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/webhint · 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
What is webhint and how does it audit .NET frontend sites?
webhint is an MIT-licensed linting tool that runs runtime audits against .NET browser-facing sites, catching accessibility, performance, security header, SEO, and PWA issues that static linters miss. It automates quality checks by pointing at your local or deployed URL and returns categorized findings ready for the team to act on.
How do I run webhint on my .NET frontend?
webhint runs via CLI against any URL. Install via npm, create a `.hintrc` configuration file in your .NET repository root, then execute webhint with your target URL (localhost during development or your deployed site). webhint uses browser automation to test runtime behavior, catching issues that static analysis cannot detect.
How do I set up webhint in my .NET repository?
Install webhint via npm, then create a `.hintrc` config file to define which hints to run and their severity levels. Add repeatable npm scripts to your `package.json` so your team can run webhint consistently. This baseline configuration ensures all developers and CI/CD pipelines audit against the same standards.
What does webhint check for in accessibility, performance, and security?
webhint performance and security headers checks validate HTTP security headers, HTTPS enforcement, accessibility compliance (WCAG), image optimization, JavaScript bundle size, and other runtime quality signals. It also audits SEO metadata, PWA manifest validity, and browser compatibility to give you a complete picture of your site's health.
Can webhint validate PWA signals and manifest in .NET projects?
Yes. webhint validates PWA signals and runtime page quality in .NET repositories by checking service worker registration, manifest.json structure, offline capability, and install prompts. These checks run at runtime, so webhint catches real-world PWA issues that your static tooling may miss.
How do I interpret webhint audit results and fix failures?
webhint returns categorized findings grouped by hint type (accessibility, performance, security, SEO, PWA). Each result includes severity, description, and remediation guidance. Review the categorized output with your team, prioritize by severity and impact, then update your .NET frontend code or configuration accordingly.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
webhint for Browser-Facing Frontends in .NET Repositories
Trigger On
- the repo ships a browser-facing site and the user asks about accessibility, performance, SEO, security headers, or page quality
- the repo has
.hintrc,hintscripts, or a served local frontend that should be audited - the team needs
(truncated - see the full file via the links below)
File tree — 2 files
catalog/Tools/webhint/skills/webhint/SKILL.md
catalog/Tools/webhint/skills/webhint/manifest.json
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 › “Audit browser-facing .NET frontend for accessibility, performance, security headers, and SEO”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
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.
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.
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.
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.
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.
More skills eslint (MIT) · roslynator (MIT)