API Contract Designer

It produces four types depending on what you ask for: structured audit reports with findings and recommendations, copy-paste OpenAPI 3.x YAML skeletons, direct answers with bullet-point summaries, or action checklists. You specify the format in your initial input or let the skill default based on your request type.

Both are supported. You tell the skill which architectural style you are working in during the scoping step, and it adjusts its resource modeling, schema design, and output conventions accordingly. For GraphQL it focuses on type definitions, query/mutation naming, and resolver contracts rather than HTTP verbs and paths.

At minimum: a description of your domain (what the API is for), who will consume it, and what you want back (audit, spec, plan). Stack details and constraints improve the specificity of naming conventions, auth recommendations, and the OAS skeleton. If you skip any of these, the skill proceeds with documented defaults.

Yes. Tell the skill you want an audit report and paste in your existing endpoint list, schema fragments, or OpenAPI file. It will evaluate consistency, flag non-idempotent operations, identify missing error handling, and produce a prioritized set of findings with recommendations.

It generates a production-ready skeleton: all paths stubbed, component schemas defined, security schemes declared, and standard response shapes filled in. Request and response bodies are modeled from your domain inputs, but business-logic-specific field validation and example values require your review before the spec is final.