Skip to main content
Skills/Content & Media/doc-site-generator

Documentation Site Generator Skill

Generates structured documentation pages from code, APIs, or specifications.

A reusable skill package for Claude Code and Cowork.

When to use this skill

  • Documenting APIs, features, or workflows
  • Creating developer-facing or end-user documentation
  • Generating structured docs from source code
  • Building comprehensive doc sites with cross-references

What this skill does

Analyzes source material (code, API specs, or descriptions), identifies the target audience, structures content into standard documentation sections, writes clear documentation with code examples, and adds cross-references and tables of contents.

How it works

  1. 1Analyze source material and identify target audience (developer, end-user, admin)
  2. 2Structure content: Overview, Prerequisites, Getting Started, Core Concepts, API Reference, Examples, Troubleshooting
  3. 3Write documentation using clear language, code examples, and inverted pyramid style
  4. 4Add cross-references and table of contents for documents over 500 words

Full Skill Definition

---
name: doc-site-generator
description: "Generates structured documentation pages from code, APIs, or specifications."
---

# Doc Site Generator

## Overview

You are a technical writing specialist focused on creating clear, structured documentation.

## Purpose

Generate comprehensive, well-organized documentation from source material.

## When to Use

When a user needs to document APIs, features, workflows, or technical systems.

## Documentation Process

## Step 1: Analyze Source Material & Define Scope

Clarify the documentation's purpose and what it should cover. Read the code, API spec, or description provided. Identify the audience (developer, end-user, admin).

## Step 2: Structure Content

Organize into: Overview, Prerequisites, Getting Started, Core Concepts, API Reference (if applicable), Examples, Troubleshooting.

## Step 3: Write Documentation

Use clear, concise language. Include code examples. Follow the inverted pyramid — most important info first.

## Step 4: Cross-Reference & Validate

Link related sections. Add a table of contents for documents over 500 words. Review the documentation for accuracy against the source material and have a subject matter expert validate technical claims.

## Error Handling

## Incomplete Source Material

Note gaps in the documentation and ask the user to provide missing details.

## Ambiguous APIs

When behavior is unclear, document the observed behavior and flag it for verification.

## Maintenance Plan

Recommend a documentation update process that is tied to the development workflow (e.g., docs updated as part of PR reviews) to prevent documentation from drifting from reality.

Summary

Generates structured documentation pages from code, APIs, or specifications. Install this skill by placing the package in ~/.claude/skills/doc-site-generator/ for personal use, or .claude/skills/doc-site-generator/ for project-specific use.

FAQs

What is this skill used for?

This skill generates comprehensive, structured documentation from source material like code or API specs.

What documentation formats does it support?

It outputs Markdown by default, structured for doc sites like Docusaurus, MkDocs, or GitBook.

Can it document an entire codebase?

Yes, but it works best when pointed at specific files or modules. Use the allowed-tools setting to give it Read and Glob access.

Download & install

Install paths

Claude Code — personal (all projects)

~/.claude/skills/doc-site-generator/SKILL.md

Claude Code — project-specific

.claude/skills/doc-site-generator/SKILL.md

Cowork — skill plugin

Upload .skill.zip via Cowork plugin manager

Compatible with Claude Code, Cowork, and any SKILL.md-compatible agent platform.

Skills in the registry are community starter templates provided as-is. skill.design and Designless do not guarantee accuracy, completeness, or fitness for any purpose. Always review, customize, and validate skills for your specific use case before deploying to production. You are responsible for the behavior of skills you install and use.