API Design Patterns

Standardize RESTful and GraphQL API design with versioning and OpenAPI documentation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mkolb22/zen-plugin --skill api-design-patterns-mkolb22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: API Design Patterns
Source: https://github.com/mkolb22/zen-plugin/tree/main/skills/api-design-patterns
Command: npx skills add https://github.com/mkolb22/zen-plugin --skill api-design-patterns-mkolb22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RESTful and GraphQL API design patterns with versioning and documentation standards to ensure scalable, consistent interfaces across teams.

Core Features & Use Cases

  • Standardized resource naming conventions, HTTP methods, and status codes for RESTful APIs.
  • GraphQL schema design patterns, pagination, and query optimization strategies.
  • OpenAPI/Swagger templating, documentation generation, and versioning approaches for stable clients.

Quick Start

Describe an API contract for a new service using the patterns in this skill.

Frequently Asked Questions about API Design Patterns

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

FAQPage Schema
How do I standardize RESTful API design patterns for consistent resource naming and HTTP methods?

Standardize RESTful API design by applying consistent resource naming conventions, HTTP methods, and status codes. This approach ensures scalable interfaces and uniform error handling across production services.

What's the best way to handle API versioning and OpenAPI documentation for stable clients?

The best way to handle API versioning and OpenAPI documentation is to use standardized templating and generation approaches. This ensures stable clients and consistent interface documentation across development teams.

How does GraphQL schema design handle pagination and query optimization strategies?

GraphQL schema design handles pagination and query optimization through standardized patterns that structure data fetching efficiently. This ensures scalable queries and robust API interfaces in production environments.

How do I implement robust error handling and pagination in production APIs?

Implement robust error handling and pagination by using standardized design patterns and concrete OpenAPI templates. This ensures consistent API behavior and scalable data retrieval across REST and GraphQL use cases.

Can I use this API design skill for both REST and GraphQL use cases?

Yes, you can use this skill for both REST and GraphQL use cases. It provides concrete templates, OpenAPI examples, and guidance covering resource naming, schema design, and versioning across both protocols.

Why does my API design lack consistency across teams despite having documentation?

API design lacks consistency across teams without standardized design patterns for versioning and documentation. Applying uniform resource naming, HTTP methods, and OpenAPI templating resolves interface inconsistencies and ensures stable clients.