html-doc-site

Transform validated HTML fragments into structured static documentation sites.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/koseki2580/skills --skill html-doc-site
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: html-doc-site
Source: https://github.com/koseki2580/skills/tree/main/skills/html-doc-site
Command: npx skills add https://github.com/koseki2580/skills --skill html-doc-site

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It prevents messy, hard-to-review documentation generation by enforcing a constrained HTML-fragment workflow that produces consistent, visually reviewable documentation sites.

Core Features & Use Cases

  • HTML fragment authoring with a strict page contract: author one <article> per fragment and keep shell chrome out of content.
  • Deterministic site generation: build split-page output for hosting and a merged single-file distribution for easy sharing.
  • Quality gates and human review: verify structure, links, headings, assets, custom elements; generate diff and a dedicated review UI that shows Old/New/Diff for changed pages.
  • Custom reusable elements: use registered custom tags (callouts, tabs, steps, before/after, code/diagrams/math wrappers) to keep fragments expressive while still validating safety boundaries.

Quick Start

Use the html-doc-site toolchain to build and verify your constrained fragments by running: python skills/html-doc-site/tools/build.py --root agents/docs

Frequently Asked Questions about html-doc-site

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

FAQPage Schema
What is constrained HTML fragment authoring for static site generation?

AI documentation site generation transforms validated constrained HTML fragments into a structured static site and a merged portable artifact. Each fragment requires a single-root `<article>` plus registered custom elements to satisfy structural validation.

Does html-doc-site require a specific page contract for each fragment?

You verify links and custom elements by running the build and verify workflow, which checks structure, headings, assets, and registered custom tags to enforce safety boundaries before generating reviewable output.

How do I export documentation to a single-file artifact for sharing?

Yes, you can review documentation changes using a dedicated review UI that generates diff and renders Old/New/Diff views for changed pages. This reviewer-facing output helps human reviewers verify modified HTML fragments.

What are the limitations of constrained HTML fragments for documentation?

Custom elements keep HTML fragments expressive while still validating safety boundaries. Registered custom tags like callouts, tabs, steps, before/after, and code wrappers allow rich content without breaking static site generation contracts.