create-documentation

Create Markdown/MDX documentation pages for Documenso features and modules.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/GitLaw-co/documenso --skill create-documentation-gitlaw-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-documentation
Source: https://github.com/GitLaw-co/documenso/tree/main/.agents/skills/create-documentation
Command: npx skills add https://github.com/GitLaw-co/documenso --skill create-documentation-gitlaw-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers and teams generate consistent, high-quality Markdown/MDX documentation for a feature or module in the Documenso documentation site.

Core Features & Use Cases

  • Identify the feature or topic to document based on context.
  • Define the audience (Users, Developers, Self-Hosters) and scope.
  • Read source code and existing docs to ensure alignment and completeness.
  • Draft a complete MDX page following the repository's structure and writing guidelines.
  • Update navigation and metadata (meta.json) when adding new pages.

Quick Start

Identify the feature to document, then draft a complete MDX page following the project's writing style and directory structure.

Frequently Asked Questions about create-documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate MDX documentation for a new feature?

To generate MDX documentation, define the feature scope and audience, review source code and existing docs, then draft a complete page following project writing guidelines and directory structure.

What is the best way to structure Markdown docs for Fumadocs?

Structuring Markdown docs for Fumadocs requires drafting complete MDX pages with proper frontmatter and updating navigation metadata in meta.json to align with the repository's framework and directory structure.

How do I update navigation metadata when adding new documentation pages?

Updating navigation metadata involves modifying the repository's meta.json file to include new MDX pages, ensuring the Fumadocs framework correctly registers and displays the added documentation sections.

Can I use this approach to document features for different audiences like developers and self-hosters?

Yes, the documentation generation process explicitly supports defining target audiences such as Users, Developers, and Self-Hosters to tailor the MDX content and scope appropriately for each reader group.

Does generating consistent documentation require reviewing existing source code?

Yes, reviewing source code and existing documentation is a required step to ensure alignment, verify technical accuracy, and maintain completeness when drafting new MDX feature pages.

What are the limitations of automated documentation generation for MDX pages?

Automated MDX page generation relies on existing repository structure and writing guidelines, requiring manual review to verify technical accuracy and ensure proper meta.json navigation updates for Fumadocs.