Guide API design decisions for REST, GraphQL, or tRPC endpoints.
npx skills add https://github.com/TimeKast/AgendaInteligente --skill api-patterns-timekast
Please help me install this Agent Skill. Skill: api-patterns Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.agent/skills/api-patterns Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill api-patterns-timekast
It helps you design and standardize web APIs so choices like REST vs GraphQL vs tRPC, response envelopes, pagination, versioning, auth, rate limiting, and documentation are made deliberately and stay consistent over time.
Ask the AI to help you design an API for your use case by specifying your consumers, preferred API style, required auth method, desired pagination approach, and the response/error format you want to standardize.
High-intent search queries and answers about installing and using this skill.
Choosing between REST, GraphQL, and tRPC depends on your consumer needs, frontend type safety, and data complexity. REST suits public clients, while GraphQL handles complex data queries and tRPC provides internal type safety.
Standardizing API response formats involves applying a consistent envelope pattern and safe error shapes. You should define uniform structures for all successful responses and errors to maintain API consistency across endpoints.
Implementing API security testing involves applying a decision checklist that covers authentication patterns, rate limiting plans, and alignment with OWASP API Top 10 vulnerabilities. This ensures endpoints are protected against common abuse vectors.
Selecting a pagination strategy depends on your dataset size and query patterns. You can choose from offset, cursor, or keyset pagination to control how clients retrieve large lists of resources efficiently.
OpenAPI documentation should include schemas, authentication methods, error responses, examples, and rate-limit details. Ensuring these elements are present makes the API documentation comprehensive for consumers.
Planning API versioning is necessary for controlled evolution of HTTP service endpoints. You can version via URI, headers, query parameters, or choose intentional no-versioning for strictly controlled internal contexts.
yu13130122297Identify uncertainties in research framing, datasets, metrics, and baselines.
ms-moarDesign REST APIs for finance applications with JWT authentication and OpenAPI documentation.
MatrixFounderAssess codebases, dependencies, and infrastructure for security vulnerabilities.
HieubkavDesign and enforce REST and GraphQL API design patterns.
