home / skills / mhattingpete / claude-skills-marketplace / technical-doc-creator

This skill generates comprehensive HTML technical documentation with code blocks, API workflows, architecture diagrams, and syntax highlighting to accelerate

npx playbooks add skill mhattingpete/claude-skills-marketplace --skill technical-doc-creator

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
2.4 KB
---
name: technical-doc-creator
description: Create HTML technical documentation with code blocks, API workflows, system architecture diagrams, and syntax highlighting. Use when users request technical documentation, API docs, API references, code examples, or developer documentation.
---

# Technical Documentation Creator

Create comprehensive HTML technical documentation with code examples and API workflows.

## When to Use

- "Create API documentation for [endpoints]"
- "Generate technical docs for [system]"
- "Document API reference"
- "Create developer documentation"

## Components

1. **Overview**: purpose, key features, tech stack
2. **Getting Started**: installation, setup, quick start
3. **API Reference**: endpoints with request/response examples
4. **Code Examples**: syntax-highlighted code blocks
5. **Architecture**: system diagram (SVG)
6. **Workflows**: step-by-step processes

## HTML Structure

```html
<!DOCTYPE html>
<html>
<head>
  <title>[API/System] Documentation</title>
  <style>
    body { font-family: system-ui; max-width: 1000px; margin: 0 auto; }
    pre { background: #1e1e1e; color: #d4d4d4; padding: 15px; border-radius: 4px; overflow-x: auto; }
    .endpoint { background: #f7fafc; padding: 15px; margin: 10px 0; border-left: 4px solid #4299e1; }
    code { background: #e2e8f0; padding: 2px 6px; border-radius: 3px; }
  </style>
</head>
<body>
  <h1>[System] Documentation</h1>
  <!-- Overview, Getting Started, API Reference, Examples -->
</body>
</html>
```

## API Endpoint Pattern

```html
<div class="endpoint">
  <h3><span style="color: #48bb78;">GET</span> /api/users/{id}</h3>
  <p>Retrieve user by ID</p>

  <h4>Request</h4>
  <pre><code>curl -X GET https://api.example.com/users/123</code></pre>

  <h4>Response</h4>
  <pre><code>{
  "id": 123,
  "name": "John Doe",
  "email": "[email protected]"
}</code></pre>
</div>
```

## Code Block Pattern

```html
<pre><code>// Installation
npm install package-name

// Usage
import { feature } from 'package-name';
const result = feature.doSomething();</code></pre>
```

## Workflow

1. Extract API endpoints, methods, parameters
2. Create overview and getting started sections
3. Document each endpoint with examples
4. Add code snippets for common operations
5. Include architecture diagram if relevant
6. Write to `[system]-docs.html`

Use semantic colors for HTTP methods: GET (green), POST (blue), DELETE (red).

Overview

This skill generates clean, self-contained HTML technical documentation tailored for APIs, developer guides, and system overviews. It produces semantic sections—overview, getting started, API reference, code examples, workflows, and an SVG architecture diagram—ready to serve as a static docs page. Output emphasizes readable code blocks, syntax highlighting styles, and HTTP method color conventions for quick scanning.

How this skill works

The skill analyzes a provided system or API specification to extract endpoints, methods, parameters, request/response samples, and common usage patterns. It builds a structured HTML document with CSS for readable code blocks, endpoint cards, and inline code elements, and can embed an SVG diagram to illustrate architecture. It writes consistent examples (curl and language snippets), method-colored headers, and a getting-started section with installation and quick-start steps.

When to use it

  • You need an HTML developer guide or API reference from an API spec or endpoint list.
  • You want a single-file docs page to host as static documentation for a service.
  • You require consistent, syntax-highlighted code examples and request/response samples.
  • You want a quick developer onboarding page with setup and usage examples.
  • You need an architecture diagram (SVG) included alongside API workflows.

Best practices

  • Provide a clear list of endpoints, methods, and sample payloads to maximize automation accuracy.
  • Include example auth tokens or authentication flows so examples are realistic but scrubbed of secrets.
  • Prefer explicit request/response JSON examples and HTTP status codes for every endpoint.
  • Supply a short description of the system stack to surface relevant getting-started steps.
  • Use semantic colors for HTTP methods (GET green, POST blue, DELETE red) to improve readability.

Example use cases

  • Generate API documentation for a microservice with CRUD endpoints and examples for each method.
  • Create a developer quick-start page with installation commands, import examples, and a minimal app snippet.
  • Produce an API reference that includes curl and JavaScript/TypeScript usage examples for every endpoint.
  • Export a single-file HTML doc that includes an SVG system architecture diagram for product handoff.
  • Document webhook payloads, retry workflows, and example consumer integration code.

FAQ

Can the output be customized for brand styles?

Yes. The generated HTML uses inline CSS that can be edited to match brand fonts, colors, and layout before deployment.

Does it include diagrams?

It can embed an SVG architecture diagram based on provided component relationships or a simple DOT-like description.