api-patterns

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

1|Updated Jan 31, 2026

Search Tags:#design #versioning #GraphQL #REST #tRPC #api-patterns

Ready to run

npx skills add https://github.com/boomNDS/soop-discoard-bot --skill api-patterns-boomnds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-patterns
Source: https://github.com/boomNDS/soop-discoard-bot/tree/main/.agents/skills/api-patterns
Command: npx skills add https://github.com/boomNDS/soop-discoard-bot --skill api-patterns-boomnds

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill guides teams in selecting the most appropriate API style (REST, GraphQL, or tRPC) for a given project, aligning architectural choices with client needs, data requirements, and development workflows.

Core Features & Use Cases

Decision framework for REST, GraphQL, and tRPC selection based on audience, frontend/backend requirements, and monorepo setups.
Guidelines for versioning, error handling, security considerations, and documentation strategy.
Use Case: For a TS monorepo with multiple frontends, this Skill helps justify the chosen API style and provides a rationale template for future audits.

Quick Start

Ask the AI to evaluate a new TS project: "Which API style (REST, GraphQL, or tRPC) is most suitable for a TS monorepo with mobile apps and a public REST gateway, and why?"

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

Choosing between REST, GraphQL, and tRPC requires evaluating your project's audience, frontend/backend requirements, and monorepo setup. This Skill provides a decision framework that aligns architectural choices with client needs and data requirements.

What is the best API style for a TypeScript monorepo with multiple frontends?▼

The best API style for a TypeScript monorepo with multiple frontends depends on specific client needs and data requirements. This Skill helps justify the chosen API style and provides a rationale template for future architectural audits.

How should I handle API versioning and error handling across different API patterns?▼

Handling API versioning and error handling across different API patterns requires consistent guidelines based on your selected style. This Skill enforces specific criteria for API versioning strategies, error handling guidelines, and security considerations to maintain consistency.

When do I need GraphQL instead of REST for evolving data requirements?▼

You need GraphQL instead of REST when your project has evolving data requirements and multi-platform clients that demand flexible querying. This Skill provides criteria to enforce API style selection based on specific data requirements and client needs.

Does tRPC work well for public API gateways and multi-platform clients?▼

Evaluating whether tRPC works well for public API gateways and multi-platform clients requires checking your specific audience and security considerations. This Skill guides teams in aligning architectural choices with client needs and development workflows.