gen-types

Regenerate frontend TypeScript types from a backend OpenAPI specification.

230|29|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/fpindej/netrock --skill gen-types-fpindej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-types
Source: https://github.com/fpindej/netrock/tree/main/.claude/skills/gen-types
Command: npx skills add https://github.com/fpindej/netrock --skill gen-types-fpindej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the frontend's understanding of the backend API's structure stays up-to-date, preventing runtime errors and improving developer experience.

Core Features & Use Cases

  • Automated Type Generation: Regenerates TypeScript types from the backend's OpenAPI specification.
  • Error Detection: Helps identify breaking API changes early in the development cycle.
  • Use Case: After a backend developer updates API endpoints or DTOs, this skill can be invoked to automatically update the corresponding frontend type definitions, ensuring consistency.

Quick Start

Run the command to regenerate frontend API types from the backend OpenAPI spec.

Frequently Asked Questions about gen-types

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

FAQPage Schema
How do I generate TypeScript types from an OpenAPI specification?

Generating TypeScript types from an OpenAPI specification involves parsing the backend API contract to automatically regenerate corresponding frontend type definitions. This ensures your frontend types stay synchronized with backend API changes.

Why should I sync frontend types with backend API changes?

Syncing frontend types with backend API changes prevents runtime errors by ensuring type safety and consistency. It helps identify breaking API contract changes early in the development cycle before they affect production.

When do I need to regenerate frontend API types?

You need to regenerate frontend API types whenever a backend developer updates API endpoints or DTOs. This maintains synchronization between your frontend and backend services after the backend OpenAPI specification changes.

What is the best way to maintain type safety between frontend and backend services?

The best way to maintain type safety is regenerating TypeScript types directly from the backend OpenAPI specification. This automated synchronization ensures consistency and improves developer experience by catching contract mismatches early.

Does this type generation approach work without additional dependencies?

Yes, this approach regenerates frontend API types from the backend OpenAPI specification without requiring additional dependencies. It operates independently to sync your frontend types with the backend API contract.