Generate Comprehensive Wiki Documentation

Generates comprehensive technical documentation pages with evidence-based depth, under non-negotiable depth requirements: trace actual code paths rather than guessing from file names, cite a file path plus function or class name for every claim, explicitly distinguish fact (from reading code) from inference, explain why something exists before what it does, and never hand-wave with phrases like "this likely handles" - the source labels these five rules non-negotiable, applying to every page it generates rather than serving as optional, situational style guidance. Its procedure plans scope, audience, and documentation budget by file count, analyzes all relevant files for patterns, algorithms, dependencies, and data flow, writes structured Markdown with diagrams and citations, then validates that file paths exist, class names are accurate, and Mermaid renders correctly.

---
title: "Page Title"
description: "One-line description"
---

Every page requires VitePress frontmatter, a minimum of two Mermaid diagrams chosen from graph, sequenceDiagram, classDiagram, stateDiagram-v2, erDiagram, or flowchart as fits the content (using autonumber in sequence diagrams, mandatory dark-mode colors - node fills #2d333b, borders #6d5dfc, text #e6edf3, with subgraph backgrounds in #161b22 bordered #30363d and connecting lines in #8b949e, plus ,color:#e6edf3 on any inline style declaration - and no <br/> tags), and citations for every non-trivial claim in (file_path:line_number) format from at least five different source files, with (Unknown - verify in path/to/check) where evidence is missing. Its fixed structure runs Overview (explaining why) through Architecture, Components, Data Flow, Implementation, to References, using tables for APIs, configs, and component summaries, and pseudocode written in a familiar language for complex code paths. VitePress compatibility rules require escaping bare generics like `List`<T> `` outside code fences and using only 3- or 6-digit hex colors.

Use it when a user asks to document a specific component, system, or feature, wants a technical deep-dive with diagrams, or a wiki catalogue section needs its content generated.

Input: a codebase or component needing documentation. Output: a structured Markdown wiki page with VitePress frontmatter, at least two dark-mode-styled Mermaid diagrams, and citations from at least five source files, following the Overview-to-References structure.

Documentation engineers and agents generating technical wiki pages who need evidence-based, code-traced accuracy rather than plausible-sounding but unverified documentation.

Beyond API and config tables, it calls for a dedicated comparison table whenever a page introduces a new technology.