api-patterns

Name: api-patterns
Availability: InStock
Author: phoenicisf

Determine the optimal API style for a project using decision criteria.

Updated Nov 7, 2025

Search Tags:#versioning #api #rest #graphql #trpc #decision-making #design-patterns

Ready to run

npx skills add https://github.com/phoenicisf/forex-analyzer --skill api-patterns-phoenicisf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-patterns
Source: https://github.com/phoenicisf/forex-analyzer/tree/main/.agents/skills/api-patterns
Command: npx skills add https://github.com/phoenicisf/forex-analyzer --skill api-patterns-phoenicisf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Decides the optimal API style (REST, GraphQL, or tRPC) for a project and provides a clear rationale to avoid architecture drift.

Core Features & Use Cases

Decision trees for selecting API style based on consumers, data needs, and team capabilities
Side-by-side trade-offs for REST, GraphQL, and tRPC including typing, caching, and versioning
Use cases and checklists to align documentation, security, and adoption across platforms

Quick Start

Ask the AI to determine the optimal API style for your project given your data models, client types, and deployment goals.

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 my API design?▼

Selecting an API style requires evaluating public APIs, monorepos, evolving data models, and multi-platform clients. Apply decision criteria covering versioning, security, and documentation alignment to justify your choice and prevent architecture drift.

When should I use GraphQL over REST for multi-platform clients?▼

GraphQL suits multi-platform clients needing tailored data payloads. Apply decision criteria to evaluate side-by-side trade-offs for REST, GraphQL, and tRPC, ensuring your choice aligns versioning, security, and documentation with your specific consumer needs.

What are the best API versioning patterns for evolving data models?▼

Optimal API versioning patterns depend on your selected API style and evolving data models. Apply decision criteria to evaluate versioning trade-offs across REST, GraphQL, and tRPC, ensuring documentation alignment and security coverage for your deployment goals.

Does tRPC work well for public APIs compared to REST?▼

tRPC is optimized for internal monorepos rather than public APIs. Apply decision criteria to evaluate side-by-side trade-offs, comparing tRPC's strong typing against REST's broader public compatibility to justify your optimal API style choice.

How do I align API security and documentation across different API styles?▼

Align API security and documentation by applying checklists tailored to your chosen API style. Use decision criteria to ensure coverage for versioning, security, and documentation alignment across REST, GraphQL, or tRPC implementations for multi-platform clients.