
API Documentation Architect
Generate complete, consistent API documentation from your codebase
What You Can Do
Claude systematically audits your API endpoints and generates comprehensive OpenAPI specifications, parameter documentation, error handling guides, and authentication flows. You get developer-ready documentation that ensures clarity, completeness, and consistency across all endpoints. The skill evaluates your existing documentation for gaps and suggests improvements to enhance developer experience.
Features
Automatically generate production-ready OpenAPI 3.0 specifications from your API code, including schemas, endpoints, methods, and request/response structures
Compare endpoints side-by-side to identify inconsistent naming conventions, response formats, error handling patterns, and parameter structures
Detect missing documentation elements like parameter descriptions, error codes, authentication requirements, rate limits, and example values
Create realistic, executable examples for each endpoint with sample payloads, headers, and responses to help developers integrate faster
Document required vs optional parameters, data types, validation rules, allowed values, and constraints for every endpoint
Systematically document all error responses, HTTP status codes, error messages, and recovery steps for each endpoint
Generate documentation for auth flows, required headers, API key formats, OAuth scopes, rate limits, and security best practices
Produce a structured audit report highlighting which endpoints lack descriptions, examples, or proper error documentation with actionable fixes
Example Output
Generated OpenAPI Spec (YAML excerpt):
post:
summary: Create user account
operationId: createUser
parameters:
- name: email
in: query
required: true
schema:
type: string
format: email
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
name: {type: string, minLength: 1}
email: {type: string, format: email}
responses:
'201':
description: User created successfully
content:
application/json:
schema:
$ref: '#/components/schemas/User'
'400':
description: Invalid email or missing required field
Consistency Audit Report:
- ✅ All POST endpoints use 201 status codes
- ⚠️ GET endpoints inconsistent: /users returns 200, /orders returns 200 (OK)
- ❌ Error responses: Some endpoints return error_code, others use code — standardize to error_code
Parameter Documentation Sample:
Parameter: api_key
Location: Header (X-API-Key)
Type: String
Required: Yes
Format: 32-character hex string
Example: a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4
Description: Your unique API authentication key
What's Included
- OpenAPI Spec Generator: Transforms your API endpoints into standards-compliant OpenAPI 3.0 YAML/JSON specifications ready for tools like Swagger UI
- Endpoint Consistency Checker: Identifies naming inconsistencies, response format variations, error handling differences, and structural misalignments across your API
- Completeness Auditor: Scans all documentation and code for missing components: parameter descriptions, examples, error codes, auth requirements, rate limits
- Example Request/Response Templates: Pre-built markdown templates for documenting realistic API usage scenarios with proper headers, payloads, and response examples
- Documentation Standards Guide: Best practices for API documentation structure, naming conventions, error messaging, and developer clarity
Who It's For
- Backend Engineers
- API Developers
- Technical Documentation Writers
- Solutions Architects
- DevOps & Platform Engineers
Best For
- REST API documentation
- Microservice API auditing
- SDK and library documentation
- Internal API standardization
- Developer portal content generation







