Manage Server Data/generate Rtk Query From Openapi
Developmentmanage-server-data/generate-rtk-query-from-openapiManage Server Data/generate Rtk Query From Openapi is an Agent Skill for development published in the reduxjs/redux-toolkit repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use this when generating RTK Query endpoints from OpenAPI schemas with @rtk-query/codegen-openapi. Covers the empty API pattern, filterEndpoints, endpointOverrides, generated tags, and reviewing generated output before it becomes part of the app.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/reduxjs/redux-toolkit/blob/HEAD/packages/rtk-query-codegen-openapi/skills/manage-server-data/generate-rtk-query-from-openapi/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/manage-server-data-generate-rtk-query-from-openapi, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Generate RTK Query From OpenAPI
Setup
// file: src/store/emptyApi.ts
import { createApi, fetchBaseQuery } from '@reduxjs/toolkit/query/react'
export const emptySplitApi = createApi({
reducerPath: 'api',
baseQuery: fetchBaseQuery({ baseUrl: '/api/' }),
endpoints: () => ({}),
})
// file: openapi-config.ts
import type { ConfigFile } from '@rtk-query/codegen-openapi'
const config: ConfigFile = {
schemaFile: 'https://petstore3.swagger.io/api/v3/openapi.json',
apiFile: './src/store/emptyApi.ts',
apiImport: 'emptySplitApi',
outputFile: './src/store/petApi.ts',
exportName: 'petApi',
hooks: true,
}
export default config
Run:
npx @rtk-query/codegen-openapi openapi-config.ts
Core Patterns
Generate into an empty shared API
import { createApi, fetchBaseQuery } from '@reduxjs/toolkit/query/react'
export const emptySplitApi = createApi({
reducerPath: 'api',
baseQuery: fetchBaseQuery({ baseUrl: '/api/' }),
endpoints: () => ({}),
})
Codegen works best when it extends a single RTK Query architecture instead of creating standalone API roots.
Filter endpoints when the schema is too broad
import type { ConfigFile } from '@rtk-query/codegen-openapi'
const config: ConfigFile = {
schemaFile: './openapi.json',
apiFile: './src/store/emptyApi.ts',
apiImport: 'emptySplitApi',
outputFile: './src/store/userApi.ts',
exportName: 'userApi',
hooks: true,
filterEndpoints: ['loginUser', /User/],
}
export default config
Start with a narrow slice of the schema if the full surface area is too noisy or the package boundaries differ from the OpenAPI file.
Use endpointOverrides to fix generation results
import type { ConfigFile } from '@rtk-query/codegen-openapi'
const config: ConfigFile = {
schemaFile: './openapi.json',
apiFile: './src/store/emptyApi.ts',
apiImport: 'emptySplitApi',
outputFile: './src/store/petApi.ts',
exportName: 'petApi',
hooks: true,
tag: true,
endpointOverrides: [
{
pattern: 'loginUser',
type: 'mutation',
},
{
pattern: /.*/,
parameterFilter: (_name, parameter) => parameter.in !== 'header',
},
{
pattern: 'getPetById',
providesTags: ['SinglePet'],
},
],
}
export default config
Review generated endpoints and override type, parameter, or tag behavior instead of hand-editing the emitted file.
Common Mistakes
HIGH Assuming generated tags are already specific enough
Wrong:
const config: ConfigFile = {
schemaFile: './openapi.json',
apiFile: './src/store/emptyApi.ts',
apiImport: 'emptySplitApi',
outputFile: './src/store/petApi.ts',
exportName: 'petApi',
tag: true,
}
Correct:
const config: ConfigFile = {
schemaFile: './openapi.json',
apiFile: './src/store/emptyApi.ts',
apiImport: 'emptySplitApi',
outputFile: './src/store/petApi.ts',
exportName: 'petApi',
tag: true,
endpointOverrides: [
{
pattern: 'getPetById',
providesTags: ['SinglePet'],
},
],
}
Generated tags are string-only by default, so they can invalidate more cache than intended.
Source: reduxjs/redux-toolkit:docs/rtk-query/usage/code-generation.mdx
HIGH Generating a brand-new API root instead of extending an empty one
Wrong:
import { createApi, fetchBaseQuery } from '@reduxjs/toolkit/query/react'
type Pet = { id: string; name: string }
export const petApi = createApi({
reducerPath: 'petApi',
baseQuery: fetchBaseQuery({ baseUrl: '/api/' }),
endpoints: (build) => ({
getPetById: build.query<Pet, string>({
query: (id) => `pets/${id}`,
}),
}),
})
Correct:
import { createApi, fetchBaseQuery } from '@reduxjs/toolkit/query/react'
export const emptySplitApi = createApi({
reducerPath: 'api',
baseQuery: fetchBaseQuery({ baseUrl: '/api/' }),
endpoints: () => ({}),
})
Generated code should plug into one RTK Query architecture so invalidation and store wiring stay coherent.
Source: reduxjs/redux-toolkit:docs/rtk-query/usage/code-generation.mdx
MEDIUM Trusting generated shapes without overrides or review
Wrong:
const config: ConfigFile = {
schemaFile: './openapi.json',
apiFile: './src/store/emptyApi.ts',
apiImport: 'emptySplitApi',
outputFile: './src/store/petApi.ts',
exportName: 'petApi',
}
Correct:
const config: ConfigFile = {
schemaFile: './openapi.json',
apiFile: './src/store/emptyApi.ts',
apiImport: 'emptySplitApi',
outputFile: './src/store/petApi.ts',
exportName: 'petApi',
endpointOverrides: [
{
pattern: 'loginUser',
type: 'mutation',
},
],
}
Real schemas often need type, parameter, or tag correction; treat generated output as reviewed source, not gospel.
Source: reduxjs/redux-toolkit:docs/rtk-query/usage/code-generation.mdx