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

Workflow

1. Choose the right target first:

- static HTML source files - generated build output such as dist/ - a reachable URL when the page is already served

1. Prefer repo-local installation and checked-in config for repeatable runs.
2. Keep HTMLHint focused on static HTML correctness and lightweight policy.
3. Add narrow scripts to package.json, for example:

- htmlhint "dist/**/*.html" - htmlhint "wwwroot/**/*.html"

1. If the repo has templating syntax that confuses the parser, lint the rendered output instead of forcing source templates through the tool.
2. Use rule overrides deliberately for real project conventions; do not disable broad classes of checks just to make a noisy first pass green.
3. Rerun the publish or frontend build flow if fixes touched generated or packaged HTML sources.

Deliver

• a repeatable static HTML lint gate
• clear targeting rules for source HTML versus rendered output
• checked-in config that matches the repo's actual page structure

Validate

• the lint target contains real static HTML, not unsupported template syntax
• commands are reproducible from repo-local dependencies
• HTMLHint ownership is kept separate from broader site-audit tooling
• fixes were verified on the built or served output that actually ships

Related skills

Related agents