dotnet-htmlhint

Lint static HTML in .NET projects for DOM structure and attribute validity.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lint static HTML in .NET projects to enforce correct DOM structure and attribute validity.

Core Features & Use Cases

  • Narrow HTML linting scope for static assets in wwwroot, dist, or published outputs.
  • Enforce basic HTML correctness, DOM structure, and attribute validity for web templates.
  • Use case: validate a product landing page stored under wwwroot before deployment.

Quick Start

Run HTMLHint against your static HTML in wwwroot or dist using your project’s config to catch DOM structure issues and invalid attributes.

Frequently Asked Questions about dotnet-htmlhint

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

FAQPage Schema
How do I lint static HTML files in a .NET project before deployment?

You can lint static HTML in .NET projects by running HTMLHint against assets in wwwroot or dist to enforce correct DOM structure and attribute validity as a pre-deploy check.

What is static HTML linting used for in web development?

Static HTML linting is used to enforce basic HTML correctness, validate DOM structure, and check attribute validity for web templates prior to deployment.

Do I need a local configuration file to run HTMLHint on wwwroot assets?

Yes, running HTMLHint on wwwroot assets requires a repo-local setup and configuration to validate target HTML files against your project rules.

Can I validate published output HTML in dist folders using this linting approach?

Yes, you can validate published output HTML in dist folders by applying HTMLHint with your project config to catch DOM structure issues and invalid attributes before release.

Does this HTML linting approach check dynamic Razor pages or only static assets?

This HTML linting approach checks only static HTML assets in wwwroot, dist, or published outputs, and does not lint dynamic Razor pages or server-rendered content.