// Import and use Kubb's generated code (types, clients, hooks, schemas, mocks). Use when writing app or test code that consumes a Kubb build.
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.
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.
| 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.extension.yaml (node_modules/@kubb/plugin-<name>/extension.yaml)
for its options, defaults and dependencies. It ships with the package, so it matches the
installed version. Use it 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 |