API Documentation Claude Skill — Generate Clean API Docs From Your Code

API documentation is one of those things every developer knows they should write but almost nobody keeps up to date. The code changes, the docs don't. Consumers of your API — whether teammates, clients, or your future self — waste time figuring out what endpoints exist and what they expect.

The API Documentation Skill generates clean, accurate API documentation directly from your actual code. Not from comments you forgot to update — from the code itself.

What the API Documentation Skill Generates

Endpoint documentation — every route with its HTTP method, URL pattern, description, and purpose.

Request format — headers required, query parameters, request body schema with field names, types, and whether they are required or optional.

Response format — response body schema for success and error cases, status codes and what they mean.

Authentication requirements — which endpoints require authentication, what auth method is used, where to pass the token.

Examples — real request and response examples that developers can use immediately.

OpenAPI compatible output — documentation structured for use with Swagger UI, Postman, or any OpenAPI-compatible tool.

How to Use the API Documentation Skill

Once installed, documenting an API route is as simple as:

Generate API documentation for this route handler
[paste your Route Handler or controller code]

Claude reads the code — the request handling logic, the validation, the response shapes — and generates complete documentation.

For a full API:

Generate documentation for all the API routes in the api/ folder

Claude works through each route and produces a complete API reference.

How to Install

1. Visit rohansurve.in/rohankit/skills/api-docs for the install guide
2. Run:

npx skills add api-docs

1. Start documenting immediately

Works for Any Stack

The skill generates documentation from code regardless of your backend framework:

• Next.js Route Handlers — the App Router API routes in your app/api/ folder
• Express routes — traditional Node.js REST API endpoints
• Dart / Flutter — documenting the API layer in your Flutter app
• FastAPI or Flask — Python backend endpoints
• Any REST API code — paste the code, get the docs

Why Code-Generated Docs Stay Accurate

The fundamental problem with manually written API docs is that they diverge from the code over time. Every refactor, every field rename, every new parameter — the docs fall behind unless someone remembers to update them.

Code-generated documentation starts from the actual implementation. Run it after any significant API change and the docs reflect the current reality. The workflow is:

1. Change the API code
2. Run Claude with the docs skill
3. Regenerate the affected documentation
4. Docs are current again

Related RohanKit Skills

• Code Review Skill — review the API code before documenting it
• TDD Skill — write tests for the API before implementation
• Next.js Full Stack Skill — Next.js API route conventions
• Git Commit Messages Skill — commit API changes and docs together cleanly
• CLAUDE.md Generator Skill — add API overview to your project CLAUDE.md

All free at rohansurve.in/rohankit.

Docs That Match Your Actual Code

The API Documentation Skill removes the gap between what your API does and what your docs say it does. Generate from code, keep it current, ship documentation that actually helps.