skills.rest
Purple-Group
Purple-GroupOFFICIAL
Explore all skills by this author →
GitHub

api-patterns

Select between REST, GraphQL, and tRPC for API design with documented rationale.

Updated Aug 27, 2026
Search Tags:#design#versioning#api#rest#graphql#patterns#trpc
One-click install
npx skills add https://github.com/Purple-Group/vector-team-cursor --skill api-patterns-purple-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-patterns
Source: https://github.com/Purple-Group/vector-team-cursor/tree/main/.cursor/skills/api-patterns
Command: npx skills add https://github.com/Purple-Group/vector-team-cursor --skill api-patterns-purple-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps teams decide between REST, GraphQL, and tRPC for API design, providing structured guidance and rationale to avoid ad-hoc choices.

Core Features & Use Cases

  • Guidance on API style selection (REST, GraphQL, tRPC) based on project context and data needs.
  • Best practices for versioning, response formats, pagination, and security considerations.
  • Real-world use cases and decision checklists to align product, frontend, and backend expectations.

Quick Start

Describe your API scenario to the AI and receive a recommended API style with rationale.

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?▼

API style selection depends on your project context and evolving data requirements; teams should use a structured decision checklist to evaluate REST, GraphQL, and tRPC, documenting the rationale for consistent style choices.

What are the best practices for API versioning and security patterns?▼

Best practices for API versioning and security patterns involve implementing structured guidelines for versioning strategy, response formats, pagination, and security considerations to align product, frontend, and backend expectations across evolving APIs.

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

Use GraphQL instead of REST when managing evolving data requirements and multi-platform clients needing flexible queries, applying a structured decision checklist to confirm it fits your specific API security and versioning patterns.

How do I document API design rationale for internal and public APIs?▼

Document API design rationale by encapsulating decision criteria, best-practice patterns, and structured checklists for style selection, versioning, error handling, and documentation standards to align team expectations across public or internal APIs.

Does tRPC work well for public APIs or is it only for internal services?▼

tRPC can be used for public APIs, but you must apply structured decision criteria regarding your multi-platform client needs and security patterns to determine if it is appropriate compared to REST or GraphQL for your specific context.

Related Skills

Explore More Software Engineering Skills→
boomNDSboomNDS

api-patterns

Select REST, GraphQL, or tRPC for TypeScript monorepo projects.

Community
Basic
agi-house-indiaagi-house-india

api-design-principles

Guide REST and GraphQL API design with versioning, error handling, and pagination patterns.

Official
Advanced
willdadywilldady
63

add-api-endpoint

Create Hono.js API endpoints with schema validation and authentication middleware.

Community
Basic
EstomEstom

code-documenter

Generate framework-aware documentation with docstrings, OpenAPI specs, and doc sites.

Community
Advanced