Docs

Generate architecture, API reference, setup, and deployment docs from codebase analysis.

17|7|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/rsts-dev/claude-buddy-marketplace --skill docs-rsts-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Docs
Source: https://github.com/rsts-dev/claude-buddy-marketplace/tree/main/plugins/buddy/skills/Docs
Command: npx skills add https://github.com/rsts-dev/claude-buddy-marketplace --skill docs-rsts-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate comprehensive technical documentation from a codebase using foundation-specific templates, architecture diagrams, and API references.

Core Features & Use Cases

  • Generates architecture diagrams (Mermaid) and component-level documentation based on the codebase.
  • Applies foundation-specific templates to produce consistent docs (Default, JHipster, MuleSoft).
  • Outputs to a docs/ directory with an auto-generated navigation README and API reference sections.

Quick Start

Invoke the docs workflow to analyze your project and generate architecture diagrams, API references, setup, and deployment documentation.

Frequently Asked Questions about Docs

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

FAQPage Schema
How do I generate technical documentation from my codebase automatically?

To generate technical documentation from a codebase, you invoke a workflow that analyzes your project source code and outputs a structured docs directory with architecture, API reference, setup, and deployment guides.

Can I create architecture diagrams from my code using Mermaid?

Yes, you can generate architecture diagrams using Mermaid by analyzing the codebase structure. The workflow renders component relationships and architecture diagrams directly within the generated documentation files.

Does this documentation generation work with JHipster and MuleSoft foundations?

Yes, documentation generation works with JHipster and MuleSoft foundations, alongside Default types. It loads foundation-specific templates to ensure the generated architecture and API reference docs match your project framework.

What is the best way to document API references for an existing project?

The best way to document API references for an existing project is to use a codebase analysis workflow that references your API specs and automatically generates an API reference section within a dedicated docs directory.

How do I create a navigation README for my project documentation?

You create a navigation README for project documentation by running a codebase analysis workflow that auto-generates a main README file to navigate the architecture, setup, and deployment documentation in the output directory.