backend-api-design
Installation
SKILL.md
Backend API Design
Design the contract first. This skill produces a reviewed API contract and the memory entries that downstream skills consume. It does not write handler code.
Coverage: REST and OpenAPI are fully covered. GraphQL and gRPC guidance is basic (schema shape, errors, limits, breaking-change checks); rely on the framework's own docs for anything deeper.
When to Use
- The user wants to design or extend an API surface, or asks "what endpoints do I need?"
- A new feature needs endpoints, and no contract exists for them yet.
- The user wants an OpenAPI/Swagger spec, a GraphQL schema, or a
.protofile. - An endpoint must be versioned, changed in a breaking way, or deprecated.
Not for:
- Building the endpoints: hand off to
backend-implementafter this skill. - Choosing the auth mechanism (sessions, JWT, OAuth) or designing login, refresh and logout endpoints: that is
backend-auth. This skill records only which endpoints need auth and which role or ownership rule applies. - Security review of an existing API:
backend-security. - Fixing a broken endpoint:
backend-debug.