api-designer

Design OpenAPI specifications and documentation for REST and GraphQL services.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/elsolal/Skillz-Claude --skill api-designer-elsolal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-designer
Source: https://github.com/elsolal/Skillz-Claude/tree/main/.claude/skills/api-designer
Command: npx skills add https://github.com/elsolal/Skillz-Claude --skill api-designer-elsolal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to design robust APIs and OpenAPI specifications for API-first projects, ensuring consistent interfaces, versioning, and thorough documentation across REST and GraphQL services.

Core Features & Use Cases

  • API-First Design: Define resources, endpoints, and data models before coding to streamline development.
  • OpenAPI & Documentation: Generate OpenAPI specs and developer docs to align frontend and backend teams.
  • Versioning & Security: Establish versioning strategies and security patterns to maintain backward compatibility.
  • Use Case: A backend team drafts an API spec for a new service, then shares the OpenAPI document with frontend teams for implementation.

Quick Start

Start by providing a PRD or architecture context and begin drafting resources, endpoints, and OpenAPI specs.

Frequently Asked Questions about api-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an OpenAPI specification for a new REST service?

To design an OpenAPI specification, provide your PRD or architecture context to define resources, endpoints, and data models, resulting in consistent API specs and validation guidance for your REST service.

What is the best way to draft API documentation for an API-first project?

The best way to draft API documentation for an API-first project is to generate OpenAPI specs from your architecture descriptions, ensuring frontend and backend teams align on endpoint definitions and security patterns.

Can I use this approach to create both REST and GraphQL endpoint definitions?

Yes, you can create both REST and GraphQL endpoint definitions by applying design patterns to your architecture descriptions, ensuring consistent naming and security across both service types.

Do I need a PRD to start designing API specifications?

You need a PRD or architecture description to start designing API specifications, as this context is required to define resources, establish versioning strategies, and generate accurate OpenAPI specs.

How do I establish API versioning and security patterns for backward compatibility?

You establish API versioning and security patterns by applying consistent design rules during the OpenAPI specification process, ensuring backward compatibility across your service endpoints.

What are the limitations of designing APIs without an existing architecture description?

Designing APIs without an architecture description limits the ability to generate accurate OpenAPI specs, as the design process requires architecture context to define resources, endpoints, and validation guidance.