Automated summary
Generates a VitePress tutorial site that explains the internal implementation of a source codebase, including architecture diagrams and code references.
Strengths
- Automates creation of structured educational documentation from source code.
- Uses Mermaid diagrams for visual architecture.
- Generates standalone deployable VitePress sites.
- Supports multiple languages (Go, TypeScript, Python).
Limitations
- Requires careful manual review of generated content for accuracy.
- Only generates Chinese-first content (may need adaptation for other languages).
- Depends on the quality of source code structure and comments.
Use when you need to create an in-depth educational tutorial for developers to understand the internal architecture and implementation details of a codebase.
Do not use for user-facing 'how to use' documentation or for very small codebases that are trivial to understand without a tutorial.
Security analysis
SafeThe skill only reads source files and generates static documentation (Markdown, config files). It does not execute any code, run shell commands, access the network, or modify files outside the specified output directory. There is no instruction to handle secrets or perform destructive actions.
No concerns found
How this analysis is madeExamples
/vitepress-tutorial ./apps/runner ./tutorials/runner-guide/vitepress-tutorial ./pkg/sandboxVitePress Source Tutorial Generator
Generate VitePress documentation sites for source code learning and analysis.
Overview
This skill creates standalone VitePress tutorial sites that teach developers how a codebase works internally. Unlike user documentation that explains "how to use", these tutorials explain "how it's implemented".
Usage
/vitepress-tutorial [source-path] [output-path]
Examples:
/vitepress-tutorial ./apps/runner ./tutorials/runner-guide/vitepress-tutorial ./pkg/sandbox
Workflow
Phase 1: Analysis
- Explore the specified source directory
- Identify key components, patterns, and architecture
- Map dependencies and data flows
- Output: Module inventory and architecture overview
User checkpoint: Confirm scope and focus areas
Phase 2: Planning
- Generate tutorial outline based on analysis
- Determine chapter structure and navigation
- Identify code sections to highlight
- Output: Tutorial structure document
User checkpoint: Approve outline before generation
Phase 3: Generation
- Create VitePress project skeleton using @project-structure.md
- Configure VitePress using @config-template.md
- Generate tutorial content following @content-guidelines.md
- Build and verify
Output Structure
{output-path}/
├── package.json
├── docs/
│ ├── .vitepress/
│ │ └── config.ts
│ ├── index.md # Homepage
│ ├── introduction/
│ │ ├── overview.md # Project overview
│ │ └── architecture.md # Architecture diagram
│ └── {modules}/ # One directory per module
│ ├── index.md
│ └── {topics}.md
└── README.md
Features
- Source References: Auto-generate
Source: path/to/file.go:123annotations - Mermaid Diagrams: Architecture, sequence, and flow diagrams
- Code Highlighting: Go, TypeScript, Python with line highlighting
- Chinese-first: Content in Chinese, code comments in English
- Standalone Deploy: Ready for Vercel, Netlify, or GitHub Pages
Configuration
The skill reads project context to customize output:
| Context | Effect |
|---------|--------|
| Go project | Uses Go code blocks, references .go files |
| TypeScript | Uses TS blocks, references .ts/.tsx files |
| Monorepo | Detects apps/, packages/ structure |
Instructions
When executing this skill:
- Always explore first - Read source files before writing tutorials
- Reference actual code - Include real code snippets with file paths
- Use Mermaid for architecture - Visual diagrams aid understanding
- Keep chapters focused - One concept per file, ~200-400 lines
- Link between chapters - Use VitePress prev/next navigation
- Include API tables - Summarize endpoints, functions, types
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/vitepress-source-tutorial-generator-mmh8qr8l/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/vitepress-source-tutorial-generator-mmh8qr8l' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/vitepress-source-tutorial-generator-mmh8qr8l/download' --output '.skill-downloads/vitepress-source-tutorial-generator-mmh8qr8l/SKILL.md.part' && mv '.skill-downloads/vitepress-source-tutorial-generator-mmh8qr8l/SKILL.md.part' '.skill-downloads/vitepress-source-tutorial-generator-mmh8qr8l/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/vitepress-source-tutorial-generator-mmh8qr8l/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.