
Covers the full API design stack: choosing between REST, GraphQL, and gRPC based on actual tradeoffs, writing OpenAPI 3.1 specs with reusable components, implementing cursor pagination that stays stable under writes, and getting HTTP semantics right (201 vs 204, idempotency, proper status codes). Treats versioning as non-negotiable from day one and pushes resource-oriented design over verb-heavy endpoints. The decision matrix for when to use which paradigm is honest about browser compatibility and microservice overhead. If you're past the "just make it work" phase and need your API to survive contact with real clients, this gives you the patterns that actually scale.
npx -y skills add absolutelyskilled/absolutelyskilled --skill api-design --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.