docs-content-typeslisted

# docs-content-types — Content Type Analysis (Diátaxis) ## Workflow 1. **Gather the docs** — get the list of pages in scope and read their content. 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. **Classify each page** — determine what Diátaxis type the page *is* (tutorial / how-to / reference / explanation), then check whether it follows that type's rules correctly. 3. **Produce report** — return one JSON issue object per finding; group by page. ## Guardrails - Do not edit any documentation files — surface findings only. - Classify first, then check — do not flag structure violations before establishing the page type. - A single page that covers the same topic across all four types is a problem; a single topic appearing in four separate pages (one per type) is correct. - Confirm with the user whether the project uses a naming convention for types (e.g., `/guides/` = how-to, `/concepts/` = explanation) before flagging navigation issues. ## 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 navigati