Audit REST and real-time API endpoints for N+1, idempotency, and pagination risks.
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill api-design-luyzkk
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/api-design Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill api-design-luyzkk
This Skill helps you design and audit APIs so they avoid common production failures like N+1 performance traps, non-idempotent write behaviors, insecure webhook handling, and inefficient pagination or protocol choices.
Ask the Skill to audit your endpoint and explain what to change so it is idempotent, paginated correctly, and avoids N+1 issues: "Analyze this API endpoint design for correctness, performance risks (N+1), idempotency, and pagination strategy: <paste endpoint description or spec here>."
High-intent search queries and answers about installing and using this skill.
You can audit your API endpoint by analyzing its behavior for N+1 performance issues, idempotency risks, and pagination strategy using decision trees and checklists that recommend safer, production-grade patterns without generating code.
Choosing between REST, GraphQL, Webhooks, WebSockets, SSE, AMQP, and gRPC requires evaluating your protocol selection needs against endpoint safety, real-time behavior, and specific query depth limits to determine the correct architectural fit.
Idempotency in API design ensures that repeated write operations produce the same result without duplicate side effects, which is essential for handling concurrency risks and securing webhook payloads in production endpoints.
You can use this API design consultation to evaluate pagination strategies and status code correctness by reviewing your DTO boundaries and endpoint specifications to identify anti-patterns and improve reliability.
You should reconsider using GraphQL over REST when your endpoints face depth limit risks or complex concurrency issues, as evaluating protocol selection tradeoffs helps determine if REST provides safer boundaries for your specific use case.
jakubciszakDesign REST APIs for Symfony backends with OpenAPI specifications and DTO-based contracts.
mikecubedDetect N+1 queries, unbounded loops, and missing pagination in code reviews.
manastalukdarAnalyze and optimize SQL/NoSQL queries with N+1 detection and index recommendations.
xloxn69Generate OpenAPI 3.0 YAML/JSON specifications for REST API endpoints.
