api-design

Generate OpenAPI specifications for REST APIs with best practices.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/victorzhuk/go-ent --skill api-design-victorzhuk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design
Source: https://github.com/victorzhuk/go-ent/tree/main/pkg/skills/core/api-design
Command: npx skills add https://github.com/victorzhuk/go-ent --skill api-design-victorzhuk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexities of designing effective APIs by providing expert guidance on best practices for REST, GraphQL, and OpenAPI specifications, ensuring maintainable and production-ready interfaces.

Core Features & Use Cases

  • Spec-First Development: Emphasizes designing APIs using formal specifications like OpenAPI, GraphQL schemas, or Protobuf.
  • Best Practices Enforcement: Guides users on implementing versioning, security, performance, and error handling.
  • Use Case: A developer needs to design a new set of RESTful endpoints for a user authentication service. They can use this Skill to generate an OpenAPI specification that adheres to REST principles, including proper HTTP methods, status codes, and request/response structures.

Quick Start

Use the api-design skill to generate an OpenAPI specification for a user management API.

Frequently Asked Questions about api-design

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

FAQPage Schema
How do I design RESTful API endpoints with proper HTTP methods and status codes?

Design RESTful API endpoints by following spec-first development principles, using correct HTTP semantics for methods and status codes, and defining clear request/response structures to ensure robust and maintainable interfaces.

What is spec-first API development and when should I use OpenAPI specifications?

Spec-first API development involves designing APIs using formal specifications like OpenAPI before writing code. You should use OpenAPI specifications to establish clear versioning, enforce best practices, and generate comprehensive documentation for production-grade APIs.

How do I generate an OpenAPI specification for a new API?

Generate an OpenAPI specification by defining your API endpoints, request/response schemas, and security requirements upfront. This approach ensures proper versioning, clear documentation, and adherence to REST principles throughout the development process.

What are the best practices for API versioning and error handling?

API versioning and error handling best practices involve implementing clear versioning strategies, using proper HTTP status codes for errors, and providing comprehensive error response structures to ensure maintainable and production-ready interfaces.

REST vs GraphQL: which API design approach should I choose?

Choose between REST and GraphQL based on your use case: REST offers standardized HTTP semantics and caching, while GraphQL provides flexible querying and reduces over-fetching. Both support spec-first development with proper versioning and documentation.

Can I use this API design guidance for both REST and GraphQL specifications?

Yes, API design guidance covers both REST and GraphQL specifications, providing best practices for spec-first development, versioning, security, and performance. It supports generating schemas and documentation for various API types and common patterns.