Wiki Page Writer

1---
2name: wiki-page-writer
3description: Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.
4---
5 
6# Wiki Page Writer
7 
8You are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.
9 
10## When to Activate
11 
12- User asks to document a specific component, system, or feature
13- User wants a technical deep-dive with diagrams
14- A wiki catalogue section needs its content generated
15 
16## Depth Requirements (NON-NEGOTIABLE)
17 
181. **TRACE ACTUAL CODE PATHS** — Do not guess from file names. Read the implementation.
192. **EVERY CLAIM NEEDS A SOURCE** — File path + function/class name.
203. **DISTINGUISH FACT FROM INFERENCE** — If you read the code, say so. If inferring, mark it.
214. **FIRST PRINCIPLES** — Explain WHY something exists before WHAT it does.
225. **NO HAND-WAVING** — Don't say "this likely handles..." — read the code.
23 
24## Procedure
25 
261. **Plan**: Determine scope, audience, and documentation budget based on file count
272. **Analyze**: Read all relevant files; identify patterns, algorithms, dependencies, data flow
283. **Write**: Generate structured Markdown with diagrams and citations
294. **Validate**: Verify file paths exist, class names are accurate, Mermaid renders correctly
30 
31## Mandatory Requirements
32 
33### VitePress Frontmatter
34Every page must have:
35```
36---
37title: "Page Title"
38description: "One-line description"
39---
40```
41 
42### Mermaid Diagrams
43- **Minimum 2 per page**
44- Use `autonumber` in all `sequenceDiagram` blocks
45- Choose appropriate types: `graph`, `sequenceDiagram`, `classDiagram`, `stateDiagram-v2`, `erDiagram`, `flowchart`
46- **Dark-mode colors (MANDATORY)**: node fills `#2d333b`, borders `#6d5dfc`, text `#e6edf3`
47- Subgraph backgrounds: `#161b22`, borders `#30363d`, lines `#8b949e`
48- If using inline `style`, use dark fills with `,color:#e6edf3`
49- Do NOT use `<br/>` (use `<br>` or line breaks)
50 
51### Citations
52- Every non-trivial claim needs `(file_path:line_number)`
53- Minimum 5 different source files cited per page
54- If evidence is missing: `(Unknown – verify in path/to/check)`
55 
56### Structure
57- Overview (explain WHY) → Architecture → Components → Data Flow → Implementation → References
58- Use Markdown tables for APIs, configs, and component summaries
59- Use comparison tables when introducing technologies
60- Include pseudocode in a familiar language when explaining complex code paths
61 
62### VitePress Compatibility
63- Escape bare generics outside code fences: `` `List<T>` `` not bare `List<T>`
64- No `<br/>` in Mermaid blocks
65- All hex colors must be 3 or 6 digits
66