What problem does it solve?
Design clean, consistent, and secure APIs — REST endpoints, GraphQL schemas, internal service contracts, and DTOs. Use this skill when the user asks to design an API, create endpoints, define a schema, plan an API surface, or says things like "design the API", "what should the endpoint look like", "create the routes", "define the contract", "design the schema". Distinct from write-docs (which documents existing code) — this designs new API contracts from requirements.
Core Features & Use Cases
- REST API design: endpoint naming, versioning, idempotency, and error handling.
- DTOs and schemas: define input/output shapes, validation, and mappings.
- Advanced patterns: CQRS, event contracts, and API versioning strategies for evolving surfaces.
- Use Case: design a new public API surface for a feature, including endpoints, schemas, and contracts, before implementation begins.
Quick Start
Design the API surface for a new feature by outlining endpoints, schemas, and DTOs from the requirements.