What problem does it solve? Teams often build APIs without documented contracts, leading to inconsistent interfaces, ambiguous error behavior, and breaking changes that surprise consumers. This Skill provides a structured procedure for designing clear, consistent, and secure API contracts before any implementation begins. ## Core Features & Use Cases - Contract Definition: Produces API contracts covering endpoint or operation definitions, request models, response models, and error definitions. - Security and Versioning Guidance: Embeds authentication, authorization, data exposure, and versioning considerations directly into the design workflow. - Template-Driven Documentation: Uses the API-Specification template with supporting integration and architecture templates for consistent documentation. - Use Case: When exposing a new service capability to external integrators, apply this Skill to define operations, validation rules, error categories, and authentication requirements so backend developers can implement without ambiguity. ## Quick Start Use the Forge-API-Design skill to design a REST API contract for a customer orders service including endpoints, request and response models, error handling, and authentication requirements.
