Results for “api-specification”

Creates a formal, AI-optimized specification for an existing GitHub Actions CI/CD workflow, focusing on behavior and requirements rather than implementation details.

Design RESTful APIs with proper resource modeling, HTTP method semantics, status codes, pagination, versioning, and documentation. Use when the user requests api design or provides relevant inputs for this workflow.

Design REST and GraphQL APIs with OpenAPI 3.1 specifications, resource modeling, versioning strategies, pagination patterns, and error handling standards.

Design consistent, developer-friendly REST APIs with conventions for resource naming, HTTP methods, status codes, pagination, filtering, error responses, versioning, and rate limiting.

Design APIs with endpoints, methods, and documentation. TRIGGERS - Use when user needs help with api-design related tasks.

Generates OpenAPI 3.1 documentation from an API codebase, auto-detecting frameworks, extracting routes and schemas, and setting up interactive docs.

Expert at designing clean, consistent, and developer-friendly APIs. Covers RESTful conventions, versioning strategies, error handling, pagination, rate limiting, and OpenAPI documentation. Designs APIs that are intuitive to use and easy to evolve. Use when "API design, REST API, RESTful, API versioning, API documentation, OpenAPI, Swagger, API error handling, pagination, rate limiting, api, rest, http, versioning, pagination, openapi, swagger" mentioned.

Write API documentation including endpoint references, OpenAPI/Swagger specs, authentication guides, SDK quickstarts, and interactive code samples. Use when documenting REST APIs, GraphQL schemas, WebSocket interfaces, or SDK libraries. Also trigger for 'API docs', 'endpoint documentation', 'OpenAPI', 'Swagger', 'SDK documentation', 'API reference', or 'REST docs'.

Design APIs with endpoints, methods, and documentation. TRIGGERS - Use when user needs help with api-design related tasks.

Designs scalable REST and GraphQL APIs, creates OpenAPI 3.1 specifications, and plans versioning, pagination, and error handling.

Tisane API Documentation API skill. Use when working with Tisane API Documentation for parse, languages, helper. Covers 8 endpoints.

Design RESTful and GraphQL APIs with proper validation, versioning, and documentation. Use when creating new endpoints, designing request/response models, or reviewing API contracts.

Update an existing specification file for a solution, optimized for Generative AI consumption based on new requirements or code changes.

Create a structured specification file for a solution component, optimized for Generative AI consumption.

Avaza API Documentation API skill. Use when working with Avaza API Documentation for api, ScheduleSeries. Covers 94 endpoints.

DeepL API Documentation API skill. Use when working with DeepL API Documentation for translate, document, glossary-language-pairs. Covers 30 endpoints.

Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation. Produces a feature specification focused on system behaviors, not implementation detail. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features — use project-documentation. Does not design the contract for an interface — use design-an-api. Does not research open-ended options before there is a feature to specify — use research.