docs-creator
Create and organize public documentation pages using Fumadocs. Use when building new documentation pages or organizing existing ones.
Best use case
docs-creator is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Create and organize public documentation pages using Fumadocs. Use when building new documentation pages or organizing existing ones.
Create and organize public documentation pages using Fumadocs. Use when building new documentation pages or organizing existing ones.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "docs-creator" skill to help with this workflow task. Context: Create and organize public documentation pages using Fumadocs. Use when building new documentation pages or organizing existing ones.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/docs-creator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How docs-creator Compares
| Feature / Agent | docs-creator | 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?
Create and organize public documentation pages using Fumadocs. Use when building new documentation pages or organizing existing ones.
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
# Documentation Creator Skill
This skill helps you build public-facing documentation in `src/content/docs`. The system is powered by [Fumadocs](https://fumadocs.dev) and supports MDX, automatic routing, and Lucide icons.
## Core Concepts
### 1. File Structure
- **Root**: `src/content/docs/`
- **Pages**: `.mdx` files become pages (e.g., `getting-started.mdx` -> `/docs/getting-started`).
- **Nested**: Folders create URL segments (e.g., `api/auth.mdx` -> `/docs/api/auth`).
- **Images**: Automatic OG image generation is enabled.
### 2. Frontmatter
Every `.mdx` file should have frontmatter:
```yaml
---
title: Page Title
description: A short description for SEO and search
icon: Box # Lucide icon name
---
```
### 3. Folder Organization (`meta.json`)
Control sidebar order, group titles, and icons by placing a `meta.json` in any directory.
```json
{
"title": "Section Name",
"icon": "Settings",
"pages": [
"index", // Matches index.mdx
"getting-started", // Matches getting-started.mdx
"---Separator---", // Adds a visual separator
"advanced" // Matches advanced/ folder or file
],
"defaultOpen": true
}
```
## Features
- **Lucide Icons**: Use any [Lucide icon name](https://lucide.dev/icons) in frontmatter `icon: Name`.
- **Components**: All standard MDX components + Fumadocs UI components (Callout, Cards, Tabs) are available.
- **Relative Links**: `[Link](./other-page)` works correctly.
- **Sitemap**: Automatically generated.
## Examples
### Basic Page (`src/content/docs/introduction.mdx`)
```mdx
---
title: Introduction
description: Getting started with our platform
icon: BookOpen
---
# Welcome
This is the introduction page.
## Next Steps
- [Installation](./installation)
- [Configuration](./config)
```
### Folder Metadata (`src/content/docs/api/meta.json`)
```json
{
"title": "API Reference",
"icon": "Webhook",
"root": true,
"pages": ["introduction", "endpoints", "authentication"]
}
```
*Note: `"root": true` makes this folder a separate tab in the sidebar if using root-level folders.*Related Skills
github-actions-docs
Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.
command-creator
This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.
skill-creator-ms
Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
github-issue-creator
Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.
docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
docstring
Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
docs-write
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
docs-review
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
langgraph-docs
Use this skill for requests related to LangGraph in order to fetch relevant documentation to provide accurate, up-to-date guidance.
gws-docs
Read and write Google Docs.
gws-docs-write
Google Docs: Append text to a document.