community-automations/api-designer

DevOps & Code

PublicClaude subagent

API Designer

Designing an API by hand means hours in YAML keeping paths, schemas, and examples consistent before a single line of server code exists. This designer drafts the whole spec from a plain description.

sonnet4 daysOpenAIOpenAPI 3.1StoplightRedocly
ClaudeClaude
ROI for
README.md

Why this subagent

Designing an API by hand means hours in YAML keeping paths, schemas, and examples consistent before a single line of server code exists. This designer drafts the whole spec from a plain description.

Describe the use case and it returns a validated OpenAPI 3.1 spec with paths, schemas, auth, and example payloads, ready to feed straight into codegen. You review and merge instead of typing brackets.

How it runs

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

Sample output

json
// Sample output
// (generated when the pipeline finishes)

Turn the described use case into a valid OpenAPI 3.1 document with named schemas, every CRUD path, request and response examples, auth, and standard error responses.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.