api-patterns

Select REST, GraphQL, or tRPC and apply API design patterns.

Updated Feb 22, 2026

Search Tags:#versioning #documentation #rest #graphql #trpc #pagination #api-design

Ready to run

npx skills add https://github.com/gelsonsimoes/wms-verticalparts --skill api-patterns-gelsonsimoes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-patterns
Source: https://github.com/gelsonsimoes/wms-verticalparts/tree/main/.agent/skills/api-patterns
Command: npx skills add https://github.com/gelsonsimoes/wms-verticalparts --skill api-patterns-gelsonsimoes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

API design decision guidance for choosing between REST, GraphQL, and tRPC, plus consistent patterns and versioning.

Core Features & Use Cases

Decision framework for API style selection (REST, GraphQL, tRPC)
Guidance prompts for response formats, versioning, and documentation
Use case examples spanning monorepos, microservices, and multi-frontend apps

Quick Start

Decide on an API style and apply the recommended patterns to your backend immediately.

Frequently Asked Questions about api-patterns

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

FAQPage Schema

How do I choose between REST, GraphQL, and tRPC for backend API design?▼

Choosing between REST, GraphQL, and tRPC for API design requires evaluating your architecture, such as microservices or monorepos. This framework provides decision criteria to evaluate response formats, pagination, and documentation standards for selecting the right style.

What is the best way to handle API versioning and documentation standards across microservices?▼

Handling API versioning and documentation across microservices requires enforcing consistent patterns and response formats. This guidance provides prompts to standardize API versioning, pagination, and documentation across different architectural styles.

How do I apply API patterns for a multi-frontend architecture?▼

Applying API patterns for a multi-frontend architecture involves selecting an API style like GraphQL or REST and enforcing consistent response formats. This approach provides use case examples to guide API decisions across multiple frontend applications.

Can I use tRPC for API design in a microservices architecture?▼

Yes, you can use tRPC for API design in a microservices architecture. The decision framework evaluates whether tRPC, REST, or GraphQL best fits your specific backend services, offering practical choices and versioning guidance for your selected approach.

When should I not use GraphQL for my backend services?▼

You should reconsider using GraphQL for backend services when your architecture is a simple monorepo where tRPC might offer more direct type safety, or when REST provides sufficient caching and pagination without the overhead of a complex schema.