api

Generate TypeScript types, API clients, and React Query hooks from Swagger/OpenAPI documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/strongerDeer/stronger-dotfiles --skill api-strongerdeer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api
Source: https://github.com/strongerDeer/stronger-dotfiles/tree/main/claude/skills/api
Command: npx skills add https://github.com/strongerDeer/stronger-dotfiles --skill api-strongerdeer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swagger/OpenAPI-based automation that generates TypeScript types, API client functions, and React Query hooks, ensuring type safety and reducing boilerplate across frontend teams. It also supports verification of consistency between Swagger specs and code, and keeps API scaffolding in sync with changes.

Core Features & Use Cases

  • Generates TypeScript types (types.ts), API client (client.ts), and React Query hooks from Swagger docs.
  • Enforces type-safety by aligning code with Swagger definitions and providing automatic validation.
  • Supports diff/update/validate workflows to track and apply changes across the codebase.
  • Supabase CRUD integration example and structured file organization for consistent APIs.

Quick Start

Run the command to generate TypeScript types, API client, and React Query hooks from your Swagger specification.

Frequently Asked Questions about api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate TypeScript types and React Query hooks from a Swagger document?

Generate TypeScript types and React Query hooks from Swagger by running an automated codegen process that parses OpenAPI definitions to produce app/api/types.ts, client.ts, and hook files, ensuring end-to-end type safety across your frontend project.

What is the best way to keep my API client in sync with Swagger spec changes?

Keeping your API client in sync with Swagger spec changes is best handled using diff, update, and validate workflows that track modifications in OpenAPI definitions and automatically regenerate the TypeScript types and API client code.

Can I use this to generate a TypeScript API client and hooks for a Supabase CRUD backend?

Yes, you can generate a TypeScript API client and hooks for a Supabase CRUD backend, as the codegen process includes a Supabase CRUD integration example and structured file organization for consistent API scaffolding.

How does Swagger-driven codegen validate consistency between OpenAPI specs and TypeScript code?

Swagger-driven codegen validates consistency by enforcing that Swagger definitions directly drive the creation of TypeScript types, API client functions, and React Query hooks, providing automatic validation to align code with the spec.

Do I need React Query to use the generated TypeScript API client?

You do not strictly need React Query to use the base generated TypeScript API client, but React Query is required if you want to utilize the automatically generated data-fetching hooks that enforce end-to-end type safety.

What files are automatically generated when parsing an OpenAPI document for TypeScript codegen?

Parsing an OpenAPI document for TypeScript codegen automatically generates app/api/types.ts for type definitions, app/api/client.ts for API client functions, and dedicated hook files for React Query integration.