Cursor Skill

adding-api-docs

Generate OpenAPI/Swagger documentation for an API, including endpoint schemas, request/response types, and interactive docs UI.

LLM Mart · 0 points · 22 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download spencerpauly-awesome-cursor-skills-resources_adding-api-docs-99cd265.zip · 1 KB
Part of spencerpauly/awesome-cursor-skills — 65 skills

Install

skills CLI npx skills add https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/adding-api-docs
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install spencerpauly-awesome-cursor-skills@llmmart
Git git clone https://github.com/spencerpauly/awesome-cursor-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole spencerpauly/awesome-cursor-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Add API Documentation (OpenAPI)

Use this skill when the user asks to add API docs, Swagger, OpenAPI spec, or generate endpoint documentation.

Steps

  1. Detect the API framework — check for Express, Fastify, Next.js API routes, Hono, Django REST Framework, FastAPI, etc.

  2. For Node.js/Express — install swagger-jsdoc and swagger-ui-express:

    npm install swagger-jsdoc swagger-ui-express
    npm install -D @types/swagger-jsdoc @types/swagger-ui-express
    

    Create the OpenAPI spec from JSDoc annotations on route handlers:

    /**
     * @openapi
     * /api/users:
     *   get:
     *     summary: List all users
     *     responses:
     *       200:
     *         description: A list of users
     */
    
  3. For Next.js API routes — create an openapi.json file manually or use next-swagger-doc to generate from route handlers. Serve the spec at /api/docs.

  4. For FastAPI (Python) — docs are built-in at /docs (Swagger UI) and /redoc. Ensure Pydantic models are used for request/response types so schemas are auto-generated.

  5. Add interactive docs UI — serve Swagger UI at a /docs route, or use Scalar/Redoc for a modern alternative:

    npm install @scalar/express-api-reference
    
  6. Define schemas — create Zod schemas (or JSON Schema) for request bodies and responses, then reference them in the OpenAPI spec. For TypeScript projects, use zod-to-openapi to generate schemas from existing Zod validators.

  7. Add authentication documentation — document the auth scheme (Bearer token, API key, OAuth2) in the OpenAPI securitySchemes section.

Notes

  • Keep the spec in sync with the actual API — generate from code when possible rather than maintaining a separate YAML file.
  • Add example values to schemas for better developer experience.
  • Version the API docs alongside the code.
Files (awesome-cursor-skills)
  • SKILL.md 2 KB
    ---
    name: adding-api-docs
    description: Generate OpenAPI/Swagger documentation for an API, including endpoint schemas, request/response types, and interactive docs UI.
    ---
    
    # Add API Documentation (OpenAPI)
    
    Use this skill when the user asks to add API docs, Swagger, OpenAPI spec, or generate endpoint documentation.
    
    ## Steps
    
    1. **Detect the API framework** — check for Express, Fastify, Next.js API routes, Hono, Django REST Framework, FastAPI, etc.
    
    2. **For Node.js/Express** — install `swagger-jsdoc` and `swagger-ui-express`:
    
       ```bash
       npm install swagger-jsdoc swagger-ui-express
       npm install -D @types/swagger-jsdoc @types/swagger-ui-express
       ```
    
       Create the OpenAPI spec from JSDoc annotations on route handlers:
    
       ```ts
       /**
        * @openapi
        * /api/users:
        *   get:
        *     summary: List all users
        *     responses:
        *       200:
        *         description: A list of users
        */
       ```
    
    3. **For Next.js API routes** — create an `openapi.json` file manually or use `next-swagger-doc` to generate from route handlers. Serve the spec at `/api/docs`.
    
    4. **For FastAPI (Python)** — docs are built-in at `/docs` (Swagger UI) and `/redoc`. Ensure Pydantic models are used for request/response types so schemas are auto-generated.
    
    5. **Add interactive docs UI** — serve Swagger UI at a `/docs` route, or use Scalar/Redoc for a modern alternative:
    
       ```bash
       npm install @scalar/express-api-reference
       ```
    
    6. **Define schemas** — create Zod schemas (or JSON Schema) for request bodies and responses, then reference them in the OpenAPI spec. For TypeScript projects, use `zod-to-openapi` to generate schemas from existing Zod validators.
    
    7. **Add authentication documentation** — document the auth scheme (Bearer token, API key, OAuth2) in the OpenAPI `securitySchemes` section.
    
    ## Notes
    
    - Keep the spec in sync with the actual API — generate from code when possible rather than maintaining a separate YAML file.
    - Add example values to schemas for better developer experience.
    - Version the API docs alongside the code.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related