What problem does it solve?
This Skill ensures API contracts are explicit and versioned before implementation to prevent frontend-backend mismatches, unstable public APIs, and undocumented integration points that break consumers.
Core Features & Use Cases
- API Contracts & OpenAPI: Provide OpenAPI 3.0 templates, component schemas, and example paths to publish a machine-readable API contract for frontend and backend teams.
- REST Principles & Response Standards: Recommend URL design, HTTP method usage, standard response envelopes, pagination meta, and a consistent error code mapping for reliable client behavior.
- Webhooks, Security & Versioning: Specify webhook payload structure, HMAC signing and validation, retry policies, rate limiting headers, and clear rules for URL vs header versioning.
- Use Case: Create a public developer API for users and posts with bearer authentication, standardized responses, documented error codes, and a webhook system for payment events to align engineering, QA, and documentation.
Quick Start
Design an OpenAPI v3 spec for a users and posts REST API with bearer token authentication, a standardized success/error payload, URL versioning, and a payment.succeeded webhook.