api-patterns

Select API patterns and design endpoint architectures for REST, GraphQL, and tRPC.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/ag47-pt/Website --skill api-patterns-ag47-pt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-patterns
Source: https://github.com/ag47-pt/Website/tree/main/.claude/skills/api-patterns
Command: npx skills add https://github.com/ag47-pt/Website --skill api-patterns-ag47-pt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers make consistent API architecture decisions by providing guidance for choosing styles, structuring responses, securing endpoints, and planning API evolution.

Core Features & Use Cases

  • API Style Selection: Compare REST, GraphQL, and tRPC approaches to choose the right architecture for different application contexts.
  • API Design Guidance: Define resource naming, response formats, authentication strategies, versioning, pagination, and documentation practices.
  • Use Case: A backend engineer designing a new SaaS platform can use this Skill to select an API approach, establish conventions, and validate implementation decisions before release.

Quick Start

Use the api-patterns skill to help design the API architecture for my new application and recommend the best patterns.

Frequently Asked Questions about api-patterns

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

FAQPage Schema
How do I design a consistent API architecture for a new backend application?

Designing a consistent API architecture requires selecting an appropriate API pattern and improving endpoint design decisions for your backend application. This process establishes conventions for resource naming, response formats, and secure service communication.

What is the best way to choose between REST, GraphQL, and tRPC for my SaaS platform?

Choosing between REST, GraphQL, and tRPC involves comparing their architectural approaches against your application context. You should evaluate these API styles based on your specific requirements for structured responses, endpoint validation, and scalable service communication.

How do I implement secure authentication and API versioning strategies?

Implementing secure authentication and API versioning requires applying dedicated API security patterns and planning your API evolution. You establish authentication strategies and versioning conventions to ensure secure service communication and scalable API updates over time.

Does this API design guidance support endpoint validation and documentation practices?

Yes, this API design guidance supports endpoint validation and documentation practices. It helps you define resource naming, pagination, and response formats, satisfying requirements for structured responses and validated endpoint design decisions before release.

When should I not use a specific API pattern for my endpoint design?

You should reconsider a specific API pattern when it fails to satisfy your requirements for structured responses, scalable API evolution, or secure service communication. Comparing REST, GraphQL, and tRPC approaches helps identify limitations and validate implementation decisions.