Document API design style selection criteria for REST, GraphQL, or tRPC.
npx skills add https://github.com/jangtrinh/EaseUI-Agent --skill api-patterns-jangtrinh
Please help me install this Agent Skill. Skill: api-patterns Source: https://github.com/jangtrinh/EaseUI-Agent/tree/main/.claude/skills/api-patterns Command: npx skills add https://github.com/jangtrinh/EaseUI-Agent --skill api-patterns-jangtrinh
## What problem does it solve? REST vs GraphQL vs tRPC selection and API pattern consistency often create confusion across teams and platforms.
## Core Features & Use Cases
### Quick Start Analyze your project requirements to choose an API style that best fits your data needs and deployment architecture.
High-intent search queries and answers about installing and using this skill.
To decide between REST, GraphQL, and tRPC, you evaluate project context like multi-platform frontends, evolving data models, and deployment architecture. The optimal API design style is identified by applying clear decision criteria based on these specific data needs.
You should use GraphQL over REST when dealing with evolving data models and multi-platform frontends that require flexible querying. The selection is based on applying consistent decision criteria to ensure your API patterns match your project's specific data fetching requirements.
The best way to enforce consistent API patterns across services is by applying practical checklists for versioning, authentication, and error handling. This ensures unified design decisions and reusable patterns that teams can adopt across all deployed services.
tRPC works well for API design in a monorepo architecture where consistent API patterns and end-to-end type safety matter. The decision to use tRPC depends on evaluating your deployment architecture and ensuring it aligns with your versioning and authentication requirements.
To document the rationale for selecting an API style, you analyze your project requirements against clear decision criteria for REST, GraphQL, or tRPC. This process records why a specific pattern was chosen, ensuring teams understand the versioning and authentication decisions.
sunLeeeTransform PRDs into technical specifications with API definitions, data models, and sequence diagrams.
fengqiliuDesign RESTful, GraphQL, and gRPC API specifications with schemas and versioning.
gelsonsimoesSelect REST, GraphQL, or tRPC and apply API design patterns.
MassimilianoPiliGenerate and validate OpenAPI 3.1 and AsyncAPI 2.6 API contracts.
