docs-structure-templateslisted

# docs-structure-templates — Structure and Formatting Analysis ## Workflow 1. **Gather the docs** — get the list of pages in scope (with metadata) and read their frontmatter and content structure. If a semantic/graph search tool over the markdown is available (self-hosted `markdown-lsp`, or a connected Docsbook workspace), prefer it — it's faster and cheaper than scanning files; otherwise read the files directly with `grep`/`find`. Prioritize Tier 1 pages (quick-start, pricing, auth, install) first. 2. **Apply checklist** — check frontmatter fields, heading hierarchy, prerequisites and setup sections, code blocks, page length/density, and callout usage. 3. **Produce report** — return one JSON issue object per finding, sorted by severity. ## Guardrails - Do not edit any documentation files — surface findings only. - Confirm with the user which frontmatter fields are required for this project (some projects have custom fields beyond `title` and `description`). - A page type determines which sections are required — don't flag a reference page for missing prerequisites. - Do not modify the `docs-content-types` skill's output — classify page type there, not here. ## Inputs This skill needs two things, by whatever means are available: - **The list of pages in scope** — a docs folder, a sitemap, or a doc graph. - **The content of each page** — read on demand. > **Acceleration (optional).** Graph/semantic search over the docs makes navigation faster and cheaper than scanning f