VitePress projects require coordinated configuration, content, themes, data loading, and deployment. This skill provides focused guidance for building maintainable VitePress sites with Vue and Markdown.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "vitepress" from https://skillstore.io/skills/antfu-vitepress.md and its manifest at https://skillstore.io/api/skills/antfu-vitepress/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
All 65 static findings are false positives from inert documentation examples, standard VitePress paths, placeholders, or Markdown formatting. No prompt injection or malicious intent was found. One separate example passes raw CMS content into generated pages without recommending validation or sanitization.
The dynamic route example passes raw Markdown or HTML from a CMS into the page content placeholder without validation or sanitization guidance. Untrusted CMS content could create stored cross-site scripting in the generated site.
The example explicitly labels the fetched value as raw Markdown or HTML and inserts it into generated page content. Exploitability depends on whether the configured CMS is trusted.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Choose build settings, base paths, output directories, and hosting configuration for a supported deployment platform.
Try These Prompts
Plan a Basic Documentation Site
Plan a VitePress site for [project]. Include the page structure, navigation, sidebar groups, search choice, and required setup steps.
Configure an Existing Site
Review my VitePress requirements for [site]. Propose configuration for metadata, clean URLs, navigation, sidebars, social links, and edit links.
Design Dynamic Content
Design VitePress data loaders and dynamic routes for [data source]. Explain file placement, watch patterns, route parameters, validation, and rendering.
Architect an Advanced VitePress Build
Architect a multilingual VitePress site with a custom theme, SSR-safe browser plugins, remote content controls, and deployment to [platform].
Best Practices
Inspect the existing VitePress configuration and theme extensions before proposing changes.
Keep browser-only code behind SSR guards and use fixed module imports.
Validate remote data, test production builds, and verify the configured base path before deployment.
Avoid
Do not copy placeholder URLs, keys, paths, or package names into production unchanged.
Do not render untrusted remote Markdown or HTML without validation and sanitization.
Do not access browser globals during server rendering without a client-only boundary.
Frequently Asked Questions
Which VitePress version does this skill cover?
The reference material targets VitePress 1.x and was generated on January 28, 2026.
Can it create a complete VitePress configuration?
Yes. It can propose configuration for site metadata, routing, Markdown, themes, search, navigation, and build options.
Does it support Vue components inside Markdown?
Yes. It covers local and global components, script setup, runtime data, templates, styles, and SSR considerations.
Can it help generate pages from data?
Yes. It covers build-time data loaders, watched local files, remote APIs, dynamic paths, parameters, and content placeholders.
Does it deploy the site automatically?
No. It provides deployment guidance and configuration examples, but users must run builds and manage hosting credentials.
How should remote HTML or Markdown be handled?
Treat remote content as untrusted. Validate its source and sanitize dangerous markup before including it in generated pages.