type-generation

Regenerate TypeScript types from an OpenAPI specification using openapi-typescript.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/andrewn6/traceway --skill type-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: type-generation
Source: https://github.com/andrewn6/traceway/tree/main/.claude/skills/type-generation
Command: npx skills add https://github.com/andrewn6/traceway --skill type-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the frontend's understanding of the backend API's structure stays up-to-date, preventing integration issues and streamlining development.

Core Features & Use Cases

  • Automatic Type Regeneration: Updates TypeScript types based on the OpenAPI specification.
  • API Synchronization: Keeps frontend code consistent with backend API changes.
  • Use Case: After a backend developer adds a new endpoint or modifies an existing data structure, this skill can be run to regenerate the necessary TypeScript types for the frontend.

Quick Start

Run the type-generation skill to sync the OpenAPI spec and regenerate frontend types.

Frequently Asked Questions about type-generation

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

FAQPage Schema
How do I sync frontend TypeScript types with an OpenAPI specification?

OpenAPI type generation prevents frontend integration issues by automatically updating TypeScript interfaces to match backend API changes. It ensures frontend code stays synchronized when backend developers modify Encore.ts or Rust daemon API routes.

How do I regenerate TypeScript types after modifying Encore.ts API routes?

Yes, openapi-typescript can convert an OpenAPI specification into usable TypeScript type definitions for frontend development. It specifically handles API route and response structure modifications from backend frameworks like Encore.ts.

What is the best way to keep frontend code consistent with backend API changes?

The best way to keep frontend code consistent with backend API changes is automatic type regeneration from an OpenAPI specification. This process directly updates TypeScript definitions to mirror modified backend response structures.

Does this type generation approach work with Rust daemon API response structures?

Yes, this type generation approach works with Rust daemon API response structures. It regenerates TypeScript types from the OpenAPI specification to reflect any modifications made to the Rust daemon API routes.

Do I need openapi-typescript to generate frontend types from my API spec?

Yes, you need the openapi-typescript package to convert your OpenAPI specification into usable TypeScript type definitions. It is a required dependency for regenerating the frontend types during synchronization.