htmlhint
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.
htmlhint validates static HTML files and generated frontend output in .NET web projects for structural correctness.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-25
htmlhint validates static HTML files and generated frontend output in .NET web projects for structural correctness. 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.
Use it when
- htmlhint can be installed via npm and configured to target your .NET project's output directories.
- Yes.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/htmlhint · 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 htmlhint static html linting and how does it work?
htmlhint is an MIT-licensed linter that enforces HTML structure and attribute correctness on static files and built output in .NET repositories. It validates rendered HTML in folders like wwwroot/ or dist/ rather than raw server-side templates, keeping validation separate from JavaScript and full-site audits. htmlhint scans for syntax errors, malformed tags, and rule violations you configure.
How do I set up htmlhint to validate static HTML files in .NET web projects?
htmlhint can be installed via npm and configured to target your .NET project's output directories. After npm install, create a .htmlhintrc configuration file in your project root, then point htmlhint at your wwwroot/ or dist/ folder. You can integrate it into your build pipeline or run it manually before deployment to catch HTML quality issues early.
Can I lint generated HTML output before deployment or build completion?
Yes. htmlhint is designed to validate rendered HTML output, making it ideal for linting generated files before deployment. You can integrate it into your CI/CD pipeline or npm build scripts to run as a quality gate. This ensures HTML structure and attributes meet your standards before the application reaches production.
How do I configure HTML structure and attribute validation rules in htmlhint?
htmlhint rules and config are managed through a .htmlhintrc file where you enable or disable specific validators. You can customize checks for tag nesting, required attributes, deprecated elements, and more. The configuration file supports both JSON and JavaScript formats, letting you tailor validation to your project's HTML standards.
How do I integrate HTML quality checks into CI/CD or npm build scripts?
Add htmlhint to your package.json scripts section with a command like "lint:html": "htmlhint dist/". Then call this script in your CI/CD pipeline (GitHub Actions, Azure Pipelines, etc.) or as part of your npm build chain. htmlhint will report violations and can fail the build if errors exceed your threshold, enforcing a static HTML quality gate.
What should I do if htmlhint reports parser errors on templated or server-side HTML?
htmlhint works best on rendered, static HTML output rather than raw server-side templates (Razor, etc.). If you encounter parser errors, ensure you're linting the built output in wwwroot/ or dist/ after your build completes. For templated HTML, run htmlhint after rendering to HTML, not on the template source files themselves.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
HTMLHint for Static HTML in .NET Repositories
Trigger On
- the repo has static HTML files, generated frontend output, or standalone templates under
wwwroot/,dist/, or other web folders - the user asks for HTML structure checks, invalid attribute detection, or basic DOM-quality linting
- the repo wants a narrow HTML gate separate from JS, CSS, and full-site runtime audits
Do Not Use For
- raw
.cshtmlor.razorsource with server-side directives; lint the rendered or published
(truncated - see the full file via the links below)
File tree — 2 files
catalog/Tools/HTMLHint/skills/htmlhint/SKILL.md
catalog/Tools/HTMLHint/skills/htmlhint/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 › “Set up HTMLHint to validate static HTML files in .NET web projects”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
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.
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.
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.
This skill configures ESLint to lint JavaScript, TypeScript, and React code in .NET repositories that include frontend assets. It detects existing configurations, installs dependencies locally, and establishes repeatable lint commands in your build pipeline. Use it when your repo has package.json, frontend source files, or explicit linting requests.
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.
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 biome (MIT) · complexity (MIT)