docs-content-typeslisted

# docs-content-types — Content Type Analysis (Diátaxis) ## Workflow 1. **Connect to Docsbook** — run `list_workspaces` to find the workspace, then `get_doc_graph` to get all pages. Offer to add the repo if not indexed. Reindex if graph is empty or stale. 2. **Read page content** — use `read_doc_sections` for each page to analyze structure and writing style. 3. **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. 4. **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. ## MCP Tools | Tool | Purpose | |------|---------| | `mcp__docsbook__list_workspaces` | Find if repo is indexed | | `mcp__docsbook__create_workspace` | Add repo to Docsbook if missing | | `mcp__docsbook__get_doc_graph` | Get full page list and structure | | `mcp__docsbook__read_doc_sections` | Read page content for classification | | `mcp__docsbook__reindex_doc_graph` | Ref