Geistdocs
Scaffold and configure Geistdocs—Vercel’s Next.js + Fumadocs documentation template—with MDX, AI chat, i18n, feedback, and Vercel deployment.
Overview
geistdocs is an agent skill most often used in Build (also Launch seo, Grow content) that guides setup and MDX authoring for Vercel’s Geistdocs + Fumadocs documentation sites.
Install
npx skills add https://github.com/vercel-labs/vercel-plugin --skill geistdocsWhat is this skill?
- Covers Geistdocs init, Fumadocs MDX syntax, configuration, and preview.geistdocs.com doc references
- Path and import triggers for geistdocs.tsx, @vercel/geistdocs, fumadocs-core/ui/mdx
- AI chat, llms.txt, i18n (pnpm translate), and feedback hooks for modern doc sites
- Deployment-oriented guidance aligned with Vercel’s documentation template repo
- Five official doc URLs referenced in skill metadata (preview.geistdocs.com docs set)
Adoption & trust: 24 installs on skills.sh; 187 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a polished docs site with MDX, search, and AI-friendly exports but keep misconfiguring Fumadocs or Geistdocs boilerplate.
Who is it for?
Solo builders shipping product or library docs on Vercel who want the official Geistdocs template and Fumadocs conventions.
Skip if: Teams committed to Docusaurus, Mintlify, or static wikis with no Next.js footprint.
When should I use this skill?
Creating documentation sites, configuring geistdocs, writing MDX content, or setting up docs infrastructure with Geistdocs/Fumadocs.
What do I get? / Deliverables
A configured Geistdocs app with structured MDX content, working navigation, and deployment-ready docs infrastructure on Vercel.
- Geistdocs-configured Next.js app with content/docs MDX tree
- Configured geistdocs.tsx and deployable documentation site
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Documentation infrastructure is authored during build even though it supports launch SEO and grow content workflows later. The docs subphase is the first commit point for geistdocs.tsx, content/docs MDX trees, and Fumadocs wiring.
Where it fits
Run geistdocs init and lay out content/docs for your API reference.
Enable llms.txt and sitemap-aligned structure for AI search visibility.
Add pnpm translate workflows and feedback widgets as docs expand.
How it compares
Opinionated Vercel docs template skill—not a generic Markdown linter or CMS migration guide.
Common Questions / FAQ
Who is geistdocs for?
Indie developers and small teams creating documentation sites with Geistdocs, Fumadocs, and Next.js on Vercel.
When should I use geistdocs?
During build when scaffolding docs, writing MDX pages, configuring geistdocs.tsx; at launch for llms.txt and SEO-ready structure; at grow when adding i18n or feedback loops.
Is geistdocs safe to install?
It guides docs setup and dependencies; review the Security Audits panel on this Prism page and pin package versions before production deploys.
SKILL.md
READMESKILL.md - Geistdocs
# Geistdocs — Vercel Documentation Template You are an expert in Geistdocs, Vercel's production-ready documentation template built with Next.js 16 and Fumadocs. It provides MDX authoring, AI-powered chat, i18n, feedback collection, search, GitHub integration, and RSS out of the box. Currently in **beta**. ## Getting Started ### Prerequisites - Node.js 18+, pnpm, GitHub account - Familiarity with MDX, Next.js, React ### Create a New Project ```bash npx @vercel/geistdocs init ``` This clones the template, prompts for a project name, installs dependencies, and removes sample content. ### Environment Setup ```bash cp .env.example .env.local pnpm dev ``` | Variable | Description | |---|---| | `AI_GATEWAY_API_KEY` | Powers AI chat; auto-configured on Vercel deployments | | `NEXT_PUBLIC_VERCEL_PROJECT_PRODUCTION_URL` | Production domain (format: `localhost:3000`, no protocol prefix); auto-set by Vercel | ## Project Structure ``` geistdocs.tsx # Root config — Logo, nav, title, prompt, suggestions, github, translations content/docs/ # MDX documentation content getting-started.mdx # → /docs/getting-started my-page.mdx # → /docs/my-page my-page.cn.mdx # → /cn/docs/my-page (i18n) .env.local # Environment variables ``` Pages auto-route from th