skills.rest
marcusagm
marcusagmCOMMUNITY
Explore all skills by this author →
Website𝕏@marcusagmGitHub

api-patterns

Select the optimal API pattern among REST, GraphQL, and tRPC for software projects.

4|Updated Jan 23, 2026
Search Tags:#versioning#documentation#GraphQL#REST#tRPC#select#API-patterns
One-click install
npx skills add https://github.com/marcusagm/Mundam --skill api-patterns-marcusagm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-patterns
Source: https://github.com/marcusagm/Mundam/tree/main/.agent/skills/api-patterns
Command: npx skills add https://github.com/marcusagm/Mundam --skill api-patterns-marcusagm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides structured guidance to select the most appropriate API pattern (REST, GraphQL, or tRPC) for a software project, helping teams design scalable and maintainable APIs.

Core Features & Use Cases

  • Decision guidance: When to choose REST, GraphQL, or tRPC based on project context.
  • Versioning & docs: Guidance on versioning strategies, response formats, and documentation best practices.
  • Use Case Scenarios: Real-world patterns for multi-platform frontends, evolving data needs, and long-term API maintenance.

Quick Start

Analyze a new project and determine the optimal API style (REST vs GraphQL vs tRPC), including versioning strategy and documentation approach.

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 a new software project?▼

Selecting the optimal API pattern involves evaluating REST, GraphQL, and tRPC based on versioning, response formats, pagination, authentication patterns, and documentation quality. This Skill analyzes those factors to recommend the best fit for scalable interfaces.

When should I use GraphQL instead of REST for evolving data requirements?▼

GraphQL suits evolving data requirements across multi-platform frontends by allowing clients to query exactly what they need. This Skill evaluates your project context to determine if GraphQL's flexible patterns provide better scalability than REST.

Does tRPC work well for API design planning in monorepos?▼

tRPC fits monorepos by providing end-to-end type safety without separate schema generation. This Skill assesses whether tRPC's patterns align with your versioning, authentication, and documentation requirements.

What's the best way to handle API versioning across different API patterns?▼

API versioning strategies vary by pattern, requiring distinct approaches for REST, GraphQL, and tRPC. This Skill provides decision guidance on selecting versioning strategies and documentation best practices aligned with your chosen architecture.

What are the limitations of using tRPC versus REST for multi-platform frontends?▼

tRPC limits multi-platform frontends by tightly coupling to TypeScript environments, whereas REST offers language-agnostic flexibility. This Skill compares these constraints to guide your API pattern selection across diverse platforms.

Related Skills

Explore More Software Engineering Skills→
melikhanmutlumelikhanmutlu

api-patterns

Guide architects in selecting REST, GraphQL, or tRPC for projects.

Community
Intermediate
mcgilly17mcgilly17
2

API Design Patterns

Design scalable APIs across REST, GraphQL, and tRPC.

Community
Advanced
bugrabilgebugrabilge
10

api-patterns

Guide API design decisions between REST, GraphQL, and tRPC architectures.

Community
Intermediate
oborchersoborchers
28

advanced-patterns

Guide implementing advanced API design patterns with OpenAPI contracts.

Community
Advanced