VitePress — Vite-Powered Documentation Site
## Overview
Best use case
VitePress — Vite-Powered Documentation Site is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
## Overview
Teams using VitePress — Vite-Powered Documentation Site should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/vitepress/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How VitePress — Vite-Powered Documentation Site Compares
| Feature / Agent | VitePress — Vite-Powered Documentation Site | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
## Overview
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# VitePress — Vite-Powered Documentation Site
## Overview
You are an expert in VitePress, the Vite-powered static site generator for documentation. You help developers build fast, beautiful documentation sites from Markdown files with Vue component integration, full-text search, i18n, and automatic navigation generation.
## Instructions
### Setup
```bash
npm add -D vitepress
npx vitepress init
# Project structure:
# docs/
# .vitepress/
# config.ts # Site configuration
# theme/ # Custom theme
# index.md # Homepage
# guide/
# getting-started.md
# installation.md
# api/
# reference.md
# Development
npx vitepress dev docs
# Build
npx vitepress build docs
```
### Configuration
```typescript
// docs/.vitepress/config.ts
import { defineConfig } from "vitepress";
export default defineConfig({
title: "My SDK",
description: "Documentation for My SDK",
themeConfig: {
logo: "/logo.svg",
nav: [
{ text: "Guide", link: "/guide/getting-started" },
{ text: "API", link: "/api/reference" },
{ text: "Changelog", link: "/changelog" },
],
sidebar: {
"/guide/": [
{
text: "Introduction",
items: [
{ text: "Getting Started", link: "/guide/getting-started" },
{ text: "Installation", link: "/guide/installation" },
{ text: "Configuration", link: "/guide/configuration" },
],
},
{
text: "Core Concepts",
items: [
{ text: "Authentication", link: "/guide/authentication" },
{ text: "Data Fetching", link: "/guide/data-fetching" },
{ text: "Error Handling", link: "/guide/error-handling" },
],
},
],
},
socialLinks: [
{ icon: "github", link: "https://github.com/org/repo" },
{ icon: "discord", link: "https://discord.gg/xxx" },
],
search: { provider: "local" }, // Built-in full-text search
editLink: {
pattern: "https://github.com/org/repo/edit/main/docs/:path",
text: "Edit this page on GitHub",
},
footer: {
message: "Released under the MIT License.",
},
},
});
```
### Markdown Features
````markdown
# Page Title
## Code Groups
::: code-group
```ts [TypeScript]
const client = new SDK({ apiKey: "xxx" });
const users = await client.users.list();
```
```python [Python]
client = SDK(api_key="xxx")
users = client.users.list()
```
```go [Go]
client := sdk.New("xxx")
users, err := client.Users.List()
```
:::
## Custom Containers
::: tip
This is a helpful tip for users.
:::
::: warning
This feature is experimental and may change.
:::
::: danger
This action cannot be undone. Proceed with caution.
:::
::: details Click to expand
Hidden content that users can reveal.
:::
## Frontmatter
```yaml
---
title: Custom Title
description: SEO description for this page
outline: [2, 3] # Show h2 and h3 in sidebar outline
prev:
text: Previous Page
link: /guide/previous
next:
text: Next Page
link: /guide/next
---
```
````
### Vue Components in Markdown
```vue
<!-- docs/.vitepress/theme/components/APIPlayground.vue -->
<template>
<div class="api-playground">
<select v-model="method">
<option>GET</option><option>POST</option><option>PUT</option>
</select>
<input v-model="url" placeholder="Enter URL" />
<button @click="send">Send</button>
<pre v-if="response">{{ response }}</pre>
</div>
</template>
<!-- Use in Markdown: -->
<!-- <APIPlayground /> -->
```
## Installation
```bash
npm add -D vitepress
```
## Examples
**Example 1: User asks to set up vitepress**
User: "Help me set up vitepress for my project"
The agent should:
1. Check system requirements and prerequisites
2. Install or configure vitepress
3. Set up initial project structure
4. Verify the setup works correctly
**Example 2: User asks to build a feature with vitepress**
User: "Create a dashboard using vitepress"
The agent should:
1. Scaffold the component or configuration
2. Connect to the appropriate data source
3. Implement the requested feature
4. Test and validate the output
## Guidelines
1. **Docs alongside code** — Keep docs in the same repo as code; changes to API and docs happen in the same PR
2. **Auto-generate API reference** — Use TypeDoc or similar to generate API pages from JSDoc/TSDoc comments
3. **Code groups for multi-language** — Show examples in all supported languages side by side
4. **Local search** — Enable built-in local search for small-medium sites; use Algolia DocSearch for large sites
5. **Edit links** — Enable "Edit this page" links; community contributions improve docs faster
6. **Frontmatter for SEO** — Set title and description in frontmatter; VitePress generates proper meta tags
7. **Vue components for interactivity** — Use Vue components for interactive examples, API playgrounds, and calculators
8. **Deploy to Vercel/Netlify** — VitePress generates static HTML; deploy anywhere with zero server costsRelated Skills
website-generator
Use when the user asks to create a website, build a site, generate a landing page, or mentions B12. Trigger phrases: "create a website", "build me a site", "website for my business", "generate a landing page", "B12 website". Trigger with 'website', 'generator'.
vitest-test-creator
Vitest Test Creator - Auto-activating skill for Test Automation. Triggers on: vitest test creator, vitest test creator Part of the Test Automation skill category.
vitepress-config-creator
Vitepress Config Creator - Auto-activating skill for Technical Documentation. Triggers on: vitepress config creator, vitepress config creator Part of the Technical Documentation skill category.
sdk-documentation-generator
Sdk Documentation Generator - Auto-activating skill for Technical Documentation. Triggers on: sdk documentation generator, sdk documentation generator Part of the Technical Documentation skill category.
database-documentation-gen
Process use when you need to work with database documentation. This skill provides automated documentation generation with comprehensive guidance and automation. Trigger with phrases like "generate docs", "document schema", or "create database documentation".
code-documentation-analyzer
Code Documentation Analyzer - Auto-activating skill for Technical Documentation. Triggers on: code documentation analyzer, code documentation analyzer Part of the Technical Documentation skill category.
recipe-batch-invite-to-event
Add a list of attendees to an existing Google Calendar event and send notifications.
playwright-explore-website
Website exploration for testing using Playwright MCP
oo-component-documentation
Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs.
go-documentation
Use when writing or reviewing documentation for Go packages, types, functions, or methods. Also use proactively when creating new exported types, functions, or packages, even if the user doesn't explicitly ask about documentation. Does not cover code comments for non-exported symbols (see go-style-core).
internationalizing-websites
Adds multi-language support to Next.js websites with proper SEO configuration including hreflang tags, localized sitemaps, and language-specific content. Use when adding new languages, setting up i18n, optimizing for international SEO, or when user mentions localization, translation, multi-language, or specific languages like Japanese, Korean, Chinese.
wiki-vitepress
Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.