api-designer

Design RESTful and GraphQL APIs and generate OpenAPI 3.1 specifications.

10|3|Updated Apr 3, 2012
One-click install
npx skills add https://github.com/liuerfire/dotfiles --skill api-designer-liuerfire
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-designer
Source: https://github.com/liuerfire/dotfiles/tree/main/agentic/skills/api-designer
Command: npx skills add https://github.com/liuerfire/dotfiles --skill api-designer-liuerfire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of designing RESTful or GraphQL APIs, ensuring they are scalable, maintainable, and developer-friendly from the outset.

Core Features & Use Cases

  • API Design & Modeling: Define resources, relationships, and operations for new APIs.
  • Specification Generation: Create comprehensive OpenAPI 3.1 specifications.
  • Best Practice Enforcement: Adheres to REST principles, versioning strategies, and error handling standards.
  • Use Case: You need to design a new microservice API for user management. This Skill will help you define the resources, endpoints, request/response schemas, and generate an OpenAPI specification.

Quick Start

Use the api-designer skill to design a REST API for managing blog posts, including endpoints for creating, reading, updating, and deleting posts, and generate an OpenAPI 3.1 specification.

Frequently Asked Questions about api-designer

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

FAQPage Schema
How do I design a REST API and generate an OpenAPI specification?

To design a REST API and generate an OpenAPI 3.1 specification, you model resources, define endpoints, and establish request/response schemas. The api-designer handles this by enforcing REST principles and outputting comprehensive specification documents.

What's the best way to structure API architecture for versioning and error handling?

The best way to structure API architecture for versioning and error handling is to apply standardized strategies during the initial modeling phase. This approach facilitates scalable and maintainable API design by defining these conventions upfront.

How does modeling resources and endpoints work for a new microservice?

Modeling resources for a microservice works by defining domain entities, their relationships, and specific operations. This process outlines the necessary endpoints and schemas to ensure the API architecture is robust and developer-friendly.

Can I use this approach to design GraphQL APIs as well as REST?

Yes, you can use this approach to design GraphQL APIs alongside REST. The api-designer facilitates API architecture planning for both paradigms, allowing you to model resources and define operations tailored to your specific architectural needs.

What is included in an OpenAPI 3.1 specification for API design?

An OpenAPI 3.1 specification includes defined resources, endpoints, request/response schemas, and best practice standards for pagination and error handling. It serves as a comprehensive blueprint to design robust APIs with confidence.

When do I need to generate an OpenAPI specification for my API?

You need to generate an OpenAPI specification when you require a standardized, machine-readable contract for your API architecture. This streamlines the complex process of designing scalable APIs, ensuring they are maintainable and developer-friendly.