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
Install
managedcode/dotnet-skills/webhint · repository language: C#
git clone https://github.com/managedcode/dotnet-skills
cp -r dotnet-skills/catalog/Tools/webhint/skills/webhint ~/.claude/skills/webhintnpx skillfed install managedcode/dotnet-skills/webhintFrequently 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)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
catalog/Tools/webhint/skills/webhint/SKILL.md
catalog/Tools/webhint/skills/webhint/manifest.json