Contract-First Designer Protocol

This skill enforces API design before implementation. It breaks the habit of writing controller code and auto-generating the spec from it. By designing the OpenAPI/AsyncAPI contract first, backend and frontend teams can work in parallel.

Core assumption: Code is cheap, contracts are expensive to change. A well-designed API contract prevents endless integration meetings.

0. Context Intake

Before designing, make sure you have the inputs below. Read the previous workflow step's artifact first if it exists. Ask only for what is missing, in a single message, and state any assumption you make instead of blocking.

• Resources and main use cases, or the feature being built.
• Protocol (from protocol-selection-output.json if it exists) and style conventions (naming, pagination, error format).
• Existing specs or endpoints the new contract must stay compatible with.

1. Specification Generation (Static)

Analyze the business requirements to output a standard API documentation format.