Select REST, GraphQL, or tRPC and document API guidelines.
npx skills add https://github.com/lchenrique/politron-ide --skill api-patterns-lchenrique
Please help me install this Agent Skill. Skill: api-patterns Source: https://github.com/lchenrique/politron-ide/tree/main/.agent/skills/api-patterns Command: npx skills add https://github.com/lchenrique/politron-ide --skill api-patterns-lchenrique
This Skill provides a structured approach to selecting API design patterns (REST, GraphQL, tRPC) and establishes consistent guidelines for responses, versioning, and pagination across projects.
Use the api-patterns skill to guide your API design decisions for a new microservice and generate a decision checklist.
High-intent search queries and answers about installing and using this skill.
Choosing between REST, GraphQL, and tRPC depends on your consumers, data shape, caching, and evolution needs. A decision checklist evaluating these factors helps establish the appropriate API style and consistent response formats.
Establishing consistent API versioning and pagination requires structured guidelines that document endpoints, schemas, and errors. Applying a decision checklist ensures repeatable patterns and scalable architecture across both small services and large multi-platform projects.
Yes, this API patterns approach applies to internal microservices and TypeScript monorepos with multi-platform frontends. It enforces documentation standards for endpoints, schemas, errors, and security considerations across varying project scales.
Documenting API security considerations and error handling requires a structured decision checklist. This enforces standards for documenting endpoints, schemas, and errors, ensuring clear API guidelines for public and internal services.
A decision checklist for API architecture is needed to systematically evaluate consumers, style, versioning, and error handling. It ensures repeatable patterns and clear guidelines when selecting REST, GraphQL, or tRPC designs.
dralgorhythmDesign scalable software systems with C4 diagrams and trade-off analysis.
ZJU-REALGenerate structured REST API documentation in Markdown from interface requirements.
ignidusStandardize REST API naming, HTTP semantics, pagination, and versioning rules.
sumik5Guide REST API endpoint design, response structure, HTTP usage, versioning, and security.
