Selects optimal API design approach from REST, GraphQL, or tRPC.
npx skills add https://github.com/uesleinasch/unac-agents --skill api-patterns-uesleinasch
Please help me install this Agent Skill. Skill: api-patterns Source: https://github.com/uesleinasch/unac-agents/tree/main/skills-shared/api-patterns Command: npx skills add https://github.com/uesleinasch/unac-agents --skill api-patterns-uesleinasch
API design guidance and decision-making to help teams choose the right API style (REST, GraphQL, or tRPC) and establish best practices for versioning, responses, and security.
Ask me to help design an API by selecting an API style and outlining governance for versioning, responses, and security.
High-intent search queries and answers about installing and using this skill.
Choosing between REST, GraphQL, and tRPC for API design requires evaluating your project context, such as multi-platform frontend needs or evolving systems, against a decision framework to select the optimal style and associated practices.
Common API design anti-patterns involve poor versioning strategies and inconsistent response formats, which you can identify and avoid by applying established guidelines and validation scripts that assess API definitions against best practices.
You can validate existing API definitions against best practices by running a dedicated validation script that assesses your code and specifications for proper versioning, response formats, and security considerations.
You should use GraphQL instead of REST for evolving backend services when your project requires flexible data fetching for multi-platform frontends, as determined by applying a comprehensive API design decision tree to your specific context.
Establishing API governance for authentication and versioning is best achieved by applying a comprehensive design framework that outlines clear guidelines, anti-patterns, and security considerations tailored to your chosen API style.
tRPC works well for multi-platform frontends when your project context aligns with its type-safe data fetching capabilities, a fit determined by evaluating your architecture through an API style decision tree.
JiliarDefine a non-revenue North Star Metric and a 5-8 input-metric tree.
DaytimeBluesGuide API design decisions between REST, GraphQL, and tRPC.
stamp-kkookkDesign and implement Java/Spring Boot backend APIs with JPA and security patterns.
xiaoniuge36Analyze code for standards compliance, bugs, performance issues, and security vulnerabilities.
