Generate Comprehensive Wiki Documentation

This skill acts as a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth. It sets five non-negotiable depth requirements: trace actual code paths instead of guessing from file names; give every claim a source, cited as file path plus function or class name; distinguish fact from inference, marking which is which; explain first principles, why something exists before what it does; and avoid hand-waving phrases like "this likely handles" in favor of reading the code.

Its procedure runs in four steps: plan the scope, audience, and documentation budget based on file count; analyze by reading all relevant files to identify patterns, algorithms, dependencies, and data flow; write structured Markdown with diagrams and citations; and validate that file paths exist, class names are accurate, and Mermaid diagrams render correctly.

Its mandatory requirements cover four areas:

• VitePress frontmatter: every page needs a title and a one-line description in frontmatter.
• Mermaid diagrams: a minimum of two per page, with autonumber in every sequenceDiagram block, the appropriate diagram type chosen (graph, sequenceDiagram, classDiagram, stateDiagram-v2, erDiagram, or flowchart), mandatory dark-mode colors (node fills #2d333b, borders #6d5dfc, text #e6edf3; subgraph backgrounds #161b22, borders #30363d, lines #8b949e; inline styles paired with ,color:#e6edf3), and no <br/> tags, using <br> or line breaks instead.
• Citations: every non-trivial claim needs a (file_path:line_number) citation, a minimum of five different source files per page, and missing evidence marked as (Unknown - verify in path/to/check).
• Structure: Overview (explaining why) leading into Architecture, Components, Data Flow, Implementation, and References, with Markdown tables for APIs, configs, and component summaries, comparison tables when introducing technologies, and pseudocode in a familiar language for complex code paths.

It also sets VitePress compatibility rules: escape bare generics outside code fences, for example writing List<T> inside backticks rather than bare in prose, avoid <br/> inside Mermaid blocks, and use 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 when a wiki catalogue section needs its content generated.

Inputs are the codebase or component to document. Outputs are a structured VitePress-compatible Markdown page with the required frontmatter, at least two Mermaid diagrams in the mandated dark-mode color scheme, at least five distinct file citations with file path and line number, and the fixed section order from Overview through References.

It is for technical writers and engineers maintaining an internal or public wiki who need documentation pages that trace real code paths and cite their sources, rather than a general narrative summary of a system.