القائمة
Import and use Kubb's generated code (types, clients, hooks, schemas, mocks). Use when writing app or test code that consumes a Kubb build.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to author a kubb.config.ts and pick the right @kubb/plugin-* packages when generating TypeScript from an OpenAPI/Swagger spec. Use whenever setting up Kubb, adding a generator, or debugging codegen output.
Remove AI-generated code slop from a branch or diff. Use after writing or generating code to strip unnecessary comments, defensive checks, `any` casts, and style that does not match the surrounding file. For prose and markdown, use the humanizer skill instead.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and SEO optimization. Overrides brevity rules for proper grammar.
Remove AI writing patterns to make documentation sound natural, specific, and human. Covers content patterns, language patterns, style patterns, and communication patterns.
Full JSDoc format guide for TypeScript, covering @example formats (short, multi-line, multi-variant), tag usage (@default, @deprecated, what to avoid), documentation patterns for properties/enums/functions, and tag order.
| name | output |
| description | Import and use Kubb's generated code (types, clients, hooks, schemas, mocks). Use when writing app or test code that consumes a Kubb build. |
This skill instructs agents on importing and using the code Kubb generates from an OpenAPI/Swagger spec.
Kubb writes generated code under the output.path from kubb.config.ts (for example ./src/gen),
organized into the folders each plugin sets through its own output.path (for example models,
clients, hooks). Generated files carry a Do not edit manually banner and are rewritten on
every kubb generate, so change them by editing the spec or config and regenerating.
Export names derive from the spec's operationId and schema names. Casing and grouping are
configurable, so read the generated files for the exact names and signatures rather than assuming
them.
Inspect the real output instead of guessing:
kubb.config.ts for the top-level output.path and each plugin's output.path.Options type (node_modules/@kubb/plugin-<name>/src/types.ts
or the published type declarations) for its options and defaults, and the plugin's docs page
(https://kubb.dev/plugins/plugin-<name>) for dependencies. Use those as the source of truth
rather than assuming an option name.Import from a folder's index.ts when output.barrel is set, otherwise import the file directly.
output.path. Edit the spec or config and rerun kubb generate.| Skill | Use For |
|---|---|
| ../config/SKILL.md | Authoring kubb.config.ts and picking plugins |