'openapi' 검색 결과

Reads an OpenAPI 3.0 specification and manually implements a type-safe Dart API layer using Dio for HTTP, Freezed or Equatable for models, and json_serializable for serialisation. Use when given an OpenAPI/Swagger file (JSON or YAML) and asked to implement the API in Flutter/Dart, create Dart models from an API schema, build a Dio API client, implement endpoints from a spec, convert openapi to dart, or set up a data/network layer from an API contract. Handles $ref resolution, oneOf union types, enums, query params, request bodies, and DioException error mapping.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples, documentation quality, contract validation (e.g. Spectral), breaking-change awareness, and handoffs to codegen — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review an OpenAPI; Improve an OpenAPI; Improve API contract; Improve API schema design. Part of cursor-rules-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates OpenAPI 3.0/3.1 specifications from Express, Next.js, Fastify, Hono, or NestJS routes. Creates complete specs with schemas, examples, and documentation that can be imported into Postman, Insomnia, or used with Swagger UI. Use when users request "generate openapi", "create swagger spec", "openapi documentation", or "api specification".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

프런트엔드와 백엔드 또는 서비스 간 API와 이벤트 명세를 먼저 정합니다. 타입을 생성하고 같은 명세로 테스트 데이터와 실제 응답을 검증해 병렬 개발 중 불일치를 줄입니다.

• 프런트엔드와 백엔드 병렬 개발
• 서비스 간 API와 이벤트 형식 통일
• 모의 응답과 운영 응답 비교

Test REST, GraphQL, and gRPC APIs with Strix using schemas, credentials, and example data. Investigate authorization flaws, excessive data exposure, and other API risks, then verify findings with requests that reproduce the issue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing an API from its specification
• Checking data access across tenants
• Verifying restrictions on administrator routes

Generate slides, documents, websites, and diagrams from natural language prompts through AnyGen OpenAPI. Manage reference uploads, check generation progress, and download finished files using commands with structured output for AI agents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generate slides or documents from written instructions
• Upload reference files for a generation task
• Check generation progress and download finished files

Compare GraphQL and RPC contracts, which describe expected API behavior, with generated clients and live handlers in a CTF sandbox. Identify hidden or outdated operations and preserve minimal request pairs that demonstrate the mismatch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare API contracts with live request handling
• Trace requests made by generated clients
• Investigate hidden or outdated API operations

Review REST API specifications with automated checks for inconsistent conventions and breaking changes—changes that disrupt existing clients. Get a design grade, improvement recommendations, and tool reports to support release reviews and API migrations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request that changes API endpoints
• Checking compatibility before an API version migration
• Establishing shared API design standards

Turn API documentation or existing scripts into reusable command-line tools that Codex can run from any folder. Builds focused read and write commands, consistent JSON output, authentication handling, installation instructions, and a companion skill.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn an API into reusable commands
• Make an internal script available from any folder
• Build a tool for downloading and searching logs

Turn plain-language requirements and optional API documentation into OpenShell sandbox network policies in YAML. Define allowed destinations, programs, and API operations, with optional middleware settings for inspecting or transforming traffic and controlling what happens when processing fails.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Restrict API access to reading operations
• Allow only specific API methods and paths
• Limit internal service access by program and IP range

Generates RESTful API documentation (OpenAPI 3.0 / Swagger spec) by scanning route definitions in code for Flask, FastAPI, Express, Gin, and other frameworks. Trigger when users ask about API documentation, OpenAPI, Swagger, endpoint docs, generating docs from code, or extracting endpoints.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Converts OpenAPI 3.0 JSON/YAML to TypeScript interfaces and type guards. This skill should be used when the user asks to generate types from OpenAPI, convert schema to TS, create API interfaces, or generate TypeScript types from an API specification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides patterns to generate comprehensive REST API documentation using SpringDoc OpenAPI 3.0 and Swagger UI in Spring Boot 3.x applications. Use when setting up API documentation, configuring Swagger UI, adding OpenAPI annotations, implementing security documentation, or enhancing REST endpoints with examples and schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

输出 OpenAPI 契约和 Mock 服务时使用。适用于 API 设计的最后一步、给前端/后端/QA 的交付。优先使用 OpenAPI 3.1 + Mock 数据覆盖所有路径 + 详细的下游交接清单。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce or review API contract documentation for Salesforce integrations: versioning policy artifacts, request/response schema specs, error code catalogs, rate limit documentation, OpenAPI generation for sObjects. Trigger keywords: Salesforce API versioning policy, API end-of-life policy, document API endpoints, REST API rate limits, OpenAPI sObjects, API contract record, error contract, errorCode catalog, 410 GONE retired API version, HTTP 300 external ID upsert, idempotency key, deprecation notice, composite subrequest limit. NOT for building the endpoint or writing the Apex REST service — use apex/apex-rest-services. NOT for upgrading the API version on your own Apex, LWC or sfdx-project.json — use devops/api-version-management.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Converts OpenAPI 3.0 JSON/YAML to TypeScript interfaces and type guards. This skill should be used when the user asks to generate types from OpenAPI, convert schema to TS, create API interfaces, or generate TypeScript types from an API specification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when documenting APIs — OpenAPI/Swagger, PHP attributes, Redocly validation, versioned specs — even when the user just says 'document this endpoint' without naming OpenAPI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates a complete, working application from an OpenAPI specification using the active framework's conventions: models, routes, validation, and tests. Use when scaffolding a service from an existing OpenAPI/Swagger spec rather than hand-writing endpoints.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates ASP.NET Minimal API endpoints with correct request/response types and complete OpenAPI (Swagger) documentation. Use when adding or reviewing Minimal API endpoints in .NET, or when generated OpenAPI output is missing schemas, status codes, or descriptions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ensure OpenAPI specs define consistent request/response schemas, error model, auth, pagination, and backward compatibility.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api/openapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling rate-limit and materialised-endpoint error responses. Use when the user says "how do I call my endpoint", "generate a client for this", or "what auth header do I use".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides patterns to generate comprehensive REST API documentation using SpringDoc OpenAPI 3.0 and Swagger UI in Spring Boot 3.x applications. Use when setting up API documentation, configuring Swagger UI, adding OpenAPI annotations, implementing security documentation, or enhancing REST endpoints with examples and schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.