SDK Scaffolder Protocol

This skill focuses on Developer Experience (DX). Auto-generated clients (via standard Swagger/OpenAPI generators) are notoriously ugly, verbose, and lack domain-specific resilience. This skill generates idiomatic code tailored to a specific language's best practices.

Core assumption: If your SDK is hard to use, developers won't use your API. An SDK is a product in itself.

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.

• The OpenAPI spec (file or contract-designer-output.json).
• Target language(s) and minimum runtime versions.
• Distribution (npm, PyPI, Go module, Maven) and authentication scheme the SDK must support.

1. Context & Language Analysis (Static)

Read the API OpenAPI specification and target language (e.g., Python httpx vs requests, or TypeScript fetch vs axios).