菜单
Use when modeling OpenAPI 3.x documents in TypeScript, including schemas, operations, parameters, responses, security schemes, components, references, extensions, media types, request bodies, and reusable utility types.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when implementing CoSec authentication with Fetcher, including CoSecConfigurer, JWT token lifecycle, token storage, refresh handling, device ID storage, multi-tenant space resolution, resource attribution, authorization headers, and 401 or 403 error handling.
Use when creating declarative TypeScript API service classes with fetcher-decorator, including @api, HTTP method decorators, path/query/header/body/request parameters, result extractors, lifecycle hooks, inheritance, and reflect-metadata setup.
Use when implementing typed event buses, serial or parallel event execution, BroadcastChannel or storage-based cross-tab messaging, handler priority, once handlers, name generation, or event synchronization across browser contexts.
Use when setting up the core Fetcher HTTP client, NamedFetcher, fetcherRegistrar, HTTP methods, path and query parameters, interceptors, timeouts, result extractors, request lifecycle, status validation, or URL templates.
Use when consuming Server-Sent Events, LLM token streams, OpenAI-style streaming chat responses, Fetcher eventstream helpers, response prototype extensions, stream termination detection, result extractors, or ReadableStream async iteration.
Use when calling OpenAI Chat Completions through Fetcher, configuring OpenAI or ChatClient, sending streaming or non-streaming chat completion requests, adding interceptors, using completion result extractors, or handling OpenAI client errors.
| name | fetcher-openapi-types |
| description | Use when modeling OpenAPI 3.x documents in TypeScript, including schemas, operations, parameters, responses, security schemes, components, references, extensions, media types, request bodies, and reusable utility types. |
$ref references.references/api.md for the full exported type map and quick reference.fetcher-openapi-generator for generation workflows.references/api.md: Detailed package API, examples, and edge-case guidance. Load it only when the task needs complete exported type lists, schema variants, operation fields, parameter and response types, security types, components, references, and extension utilities.