Generate a complete, production-ready documentation site for any project.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncreate-docsExecute the skills CLI command in your project's root directory to begin installation:
Fetches create-docs from nuxt-content/docus and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate create-docs. Access via /create-docs in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
2.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2.7K
stars
Generate a complete, production-ready documentation site for any project.
Detect from lock files, default to npm if none found:
| Lock File | PM | Install | Run | Add |
|---|---|---|---|---|
pnpm-lock.yaml |
pnpm | pnpm install |
pnpm run |
pnpm add |
package-lock.json |
npm | npm install |
npm run |
npm install |
yarn.lock |
yarn | yarn install |
yarn |
yarn add |
bun.lockb |
bun | bun install |
bun run |
bun add |
Use [pm] as placeholder in commands below.
Check for:
├── pnpm-workspace.yaml → pnpm monorepo
├── turbo.json → Turborepo monorepo
├── lerna.json → Lerna monorepo
├── nx.json → Nx monorepo
├── apps/ → Apps directory (monorepo)
├── packages/ → Packages directory (monorepo)
├── docs/ → Existing docs (avoid overwriting)
├── README.md → Main documentation source
└── src/ or lib/ → Source code location
| Project Type | Target Directory | Workspace Entry |
|---|---|---|
| Standard project | ./docs |
N/A |
Monorepo with apps/ |
./apps/docs |
apps/docs |
Monorepo with packages/ |
./docs |
docs |
Existing docs/ folder |
Ask user or ./documentation |
— |
| File | Extract |
|---|---|
README.md |
Project name, description, features, usage examples |
package.json |
Name, description, dependencies, repository URL |
src/ or lib/ |
Exported functions, composables for API docs |
Check if project needs multi-language docs:
| Indicator | Action |
|---|---|
@nuxtjs/i18n in dependencies |
Use i18n template |
locales/ or i18n/ folder exists |
Use i18n template |
| Multiple language README files | Use i18n template |
| User explicitly mentions multiple languages | Use i18n template |
| None of the above | Use default template |
Default template:
[docs-location]/
├── app/ # Optional: for customization
│ ├── app.config.ts
│ ├── components/
│ ├── layouts/
│ └── pages/
├── content/
│ ├── index.md
│ └── 1.getting-started/
│ ├── .navigation.yml
│ └── 1.introduction.md
├── public/
│ └── favicon.ico
├── package.json
└── .gitignore
i18n template (if multi-language detected):
[docs-location]/
├── app/
│ └── app.config.ts
├── content/
│ ├── en/
│ │ ├── index.md
│ │ └── 1.getting-started/
│ │ ├── .navigation.yml
│ │ └── 1.introduction.md
│ └── fr/ # Or other detected languages
│ ├── index.md
│ └── 1.getting-started/
│ ├── .navigation.yml
│ └── 1.introduction.md
├── nuxt.config.ts # Required for i18n config
├── public/
│ └── favicon.ico
├── package.json
└── .gitignore
Default:
{
"name": "[project-name]-docs",
"private": true,
"scripts": {
"dev": "nuxt dev --extends docus",
"build": "nuxt build --extends docus",
"generate": "nuxt generate --extends docus",
"preview": "nuxt preview --extends docus"
},
"dependencies": {
"docus": "latest",
"better-sqlite3": "^12.5.0",
"nuxt": "^4.2.2"
}
}
i18n (add @nuxtjs/i18n):
{
"name": "[project-name]-docs",
"private": true,
"scripts": {
"dev": "nuxt dev --extends docus",
"build": "nuxt build --extends docus",
"generate": "nuxt generate --extends docus",
"preview": "nuxt preview --extends docus"
},
"dependencies": {
"@nuxtjs/i18n": "^10.2.1",
"docus": "latest",
"better-sqlite3": "^12.5.0",
"nuxt": "^4.2.2"
}
}
export default defineNuxtConfig({
modules: ['@nuxtjs/i18n'],
i18n: {
locales: [
{ code: 'en', language: 'en-US', name: 'English' },
{ code: 'fr', language: 'fr-FR', name: 'Français' }
],
defaultLocale: 'en'
}
})
node_modules
.nuxt
.output
.data
dist
onlyBuiltDependencies (required for better-sqlite3):packages:
- 'apps/*'
- 'docs'
onlyBuiltDependencies:
- better-sqlite3
{
"scripts": {
"docs:dev": "pnpm run --filter [docs-package-name] dev"
}
}
Or with directory path:
{
"scripts": {
"docs:dev": "cd docs && pnpm dev"
}
}
{
"workspaces": ["apps/*", "docs"],
"scripts": {
"docs:dev": "npm run dev --workspace=docs"
}
}
Use templates from references/templates.md.
CRITICAL: MDC Component Naming
All Nuxt UI components in MDC must use the u- prefix:
| Correct | Wrong |
|---|---|
::u-page-hero |
::page-hero |
::u-page-section |
::page-section |
:::u-page-feature |
:::page-feature |
:::u-button |
:::button |
::::u-page-card |
::::page-card |
Without the u- prefix, Vue will fail to resolve the components.
content/
├── index.md # Landing page
├── 1.getting-started/
│ ├── .navigation.yml
│ ├── 1.introduction.md
│ └── 2.installation.md
├── 2.guide/
│ ├── .navigation.yml
│ ├── 1.configuration.md
│ ├── 2.authentication.md
│ └── 3.deployment.md
└── 3.api/ # If applicable
├── .navigation.yml
└── 1.reference.md
index.md) - Hero + features gridFor writing style, see references/writing-guide.md. For MDC components, see references/mdc-components.md.
Docus automatically includes MCP server (/mcp) and llms.txt generation. No configuration needed.
Do NOT add AI Integration sections to the landing page. These features work automatically.
Optionally mention in the introduction page:
::note
This documentation includes AI integration with MCP server and automatic `llms.txt` generation.
::
export default defineAppConfig({
docus: {
name: '[Project Name]',
description: '[Project description]',
url: 'https://[docs-url]',
socials: {
github: '[org]/[repo]'
}
}
})
If the project has a design system or brand colors, customize the docs theme.
Create app/assets/css/main.css:
@import "tailwindcss";
@import "@nuxt/ui";
@theme {
/* Custom font */
--font-sans: 'Inter', sans-serif;
/* Custom container width */
--ui-container: 90rem;
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
langchain-ai/deepagents
upstash/context7
zrong/skills
google-gemini/gemini-cli
lombiq/tailwind-agent-skills
yejinlei/pdf-ocr-skill
create-docs has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in create-docs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
create-docs fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
create-docs is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: create-docs is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added create-docs from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
create-docs fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
create-docs reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend create-docs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
create-docs has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 41