dotnet-webhint

Audit .NET frontends with webhint for accessibility, performance, and security issues.

8|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-webhint-postpartum-genushyacinthus29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-webhint
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-webhint
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-webhint-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

webhint-based audits for browser-facing .NET frontends help teams catch accessibility, performance, and security gaps early.

Core Features & Use Cases

  • CLI-driven audits against local or deployed frontend outputs
  • Guidance & remediation notes for accessibility, performance, and security issues
  • Use Case: Imagine you have a SPA in a .NET project; use this skill to run webhint and surface actionable findings

Quick Start

Run webhint against your .NET frontend site to surface actionable audit results.

Frequently Asked Questions about dotnet-webhint

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

FAQPage Schema
How do I run a webhint audit on a .NET frontend?

To run a webhint audit, you need a local or deployed URL, a checked-in .hintrc configuration file, and a repo-local setup to execute CLI-based audits consistently within your .NET workflow.

What kind of issues does a webhint frontend audit detect in a .NET project?

A webhint frontend audit surfaces accessibility, performance, and security issues in browser-facing .NET frontends, providing guidance and remediation notes to help teams catch these gaps early.

Can I use webhint to audit a SPA served by a .NET application?

Yes, you can use webhint to audit a SPA in a .NET project by running CLI-driven audits against the local or deployed frontend output to surface actionable findings.

Do I need a checked-in .hintrc file to perform accessibility audits on .NET sites?

Yes, a checked-in .hintrc file is required to ensure the webhint accessibility, performance, and security audits run consistently across your .NET repository environment.

What's the best way to catch security and performance gaps early in .NET frontend development?

Running webhint audits against browser-facing .NET frontends helps teams catch security and performance gaps early by identifying issues and providing actionable remediation guidance during development.

Does webhint work with deployed .NET frontend URLs or only local sites?

webhint supports CLI-driven audits against both local and deployed frontend outputs, allowing you to target any reachable URL from your .NET repository setup.