vitepress-learning-site

name

vitepress-learning-site

description

Build a multi-page, research-grade VitePress learning site from scratch for a topic the user wants to deeply understand. Drives an interview-first workflow — grills the user one decision at a time on scope, audience, language, depth, and boundaries; gathers primary sources before any writing begins; scaffolds a VitePress project with Mermaid (and optionally KaTeX); dispatches parallel writing sub-agents under strict fact-first discipline (mandatory source citations per file, explicit uncertainty markers, zero speculation); runs an independent external audit pass (e.g., via a second LLM/agent such as Codex) for fact-check and structural critique; verifies rendering in a real browser with dev tools (build success alone is insufficient — math layout, Mermaid SVGs, console errors all get checked). Use this skill whenever the user asks to "build a learning site", "make a study reference", "produce a structured explainer for X", wants a VitePress-based "I want to deeply understand X" outcome, or says things like "ドキュメントサイト作って" / "学習リファレンス作って" / "Xの内部を解説するサイト作って". Also trigger when the user is about to take on a self-study project that would benefit from a persistent multi-page written resource. Do NOT use for single-page READMEs, blog-style writeups, or product-landing docs — this skill is for multi-page, structured, long-form learning deliverables only.

VitePress Learning Site Builder

You are helping the user build a research-grade, multi-page VitePress learning site on a specific topic. The point is for the user to deeply learn the topic — not to produce a polished marketing site — so content correctness and source traceability beat aesthetic polish.

Core principles (read before acting)

1. Interview first, execute second. The user rarely knows exactly what they want until you grill them. Never assume scope, audience, or depth. Surface decisions with AskUserQuestion one at a time when it matters. Record the answers and the why.

2. Primary sources are non-negotiable. Writing sub-agents must consult specs, official docs, standard references, or source code — not blogs, forums, or memory — before writing. Every page ends with a (or equivalent) section that cites specific URLs, spec sections, or file paths.