skills.rest
gabriellpequeno
gabriellpequenoCOMMUNITY
Explore all skills by this author →
GitHub

api-patterns

Define and enforce API design patterns across REST, GraphQL, and tRPC implementations.

8|Updated Apr 8, 2026
Search Tags:#versioning#rest#graphql#guidelines#trpc#contracts#api-design
One-click install
npx skills add https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo --skill api-patterns-gabriellpequeno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-patterns
Source: https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo/tree/main/.cursor/skills/api-patterns
Command: npx skills add https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo --skill api-patterns-gabriellpequeno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams design and review REST, GraphQL, and tRPC APIs by enforcing consistent response formats, clear contracts, and scalable versioning strategies across services.

Core Features & Use Cases

  • Establishes naming conventions for endpoints and resources across API surfaces.
  • Defines standardized response envelopes and error handling to reduce friction in integration.
  • Provides guidance for versioning strategies and API governance when multiple teams contribute to an API.

Quick Start

Design and review an API contract for a new resource using REST, GraphQL, or tRPC guidelines.

Frequently Asked Questions about api-patterns

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

FAQPage Schema
How do I establish consistent API design patterns across REST, GraphQL, and tRPC?▼

Establish consistent API design patterns by defining standardized response envelopes, clear contracts, and uniform endpoint naming conventions across REST, GraphQL, and tRPC implementations. This reduces integration friction and ensures scalable API governance across multiple contributing teams.

What is the best way to handle API versioning strategies in a multi-service environment?▼

The best way to handle API versioning in multi-service environments is to apply scalable versioning guidelines alongside standardized error handling. This ensures clear contracts and consistent response formats when multiple teams contribute to evolving API surfaces.

How do I standardize error handling and response envelopes for multi-tenant APIs?▼

Standardize error handling and response envelopes for multi-tenant APIs by enforcing consistent design guidelines across all services. Applying standardized response formats reduces integration friction and maintains clear contracts across different API implementations.

When do I need formal API governance and standardized contracts for my endpoints?▼

You need formal API governance and standardized contracts when multiple teams contribute to an API. Establishing naming conventions, versioning strategies, and standardized response envelopes ensures scalable governance and reduces integration friction across services.

Does this API design guidance work for both GraphQL and tRPC implementations?▼

Yes, this API design guidance works for GraphQL and tRPC implementations by applying consistent design patterns across all surfaces. It defines clear contracts, endpoint naming conventions, and versioning strategies tailored for REST, GraphQL, and tRPC environments.

Related Skills

Explore More Software Engineering Skills→
mcgilly17mcgilly17
2

API Design Patterns

Design scalable APIs across REST, GraphQL, and tRPC.

Community
Advanced
hffmnnjhffmnnj
39

api-docs

Generate API reference documentation from OpenAPI specs and GraphQL schemas.

Community
Advanced
jx1100370217jx1100370217
4

ios-ui-ux-design

Design iOS interfaces following Apple's Human Interface Guidelines.

Community
Basic
MomoDavilukeMomoDaviluke
2

api-design-standards

Enforce REST API standards with unified responses, DTO separation, and pagination.

Community
Advanced