output-dev-types-file

Generate TypeScript types and Zod schemas for Output SDK workflows.

430|12|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/growthxai/output --skill output-dev-types-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: output-dev-types-file
Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-types-file
Command: npx skills add https://github.com/growthxai/output --skill output-dev-types-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of strongly-typed TypeScript definitions and Zod schemas for Output SDK workflows, reducing manual boilerplate and ensuring consistent input/output validation across projects.

Core Features & Use Cases

  • Generates WorkflowInput, StepInput, and StepOutput schemas using z from @outputai/core
  • Exports TypeScript types that mirror the schemas for compile-time type safety
  • Supports common patterns for inputs/outputs, including optional fields, defaults, and validation describes
  • Real-world use: define a new workflow and auto-generate types to accelerate integration with the Output SDK

Quick Start

Run the type-generation tool against your schemas to produce types.ts files and update your codebase accordingly.

Frequently Asked Questions about output-dev-types-file

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

FAQPage Schema
How do I generate TypeScript types and Zod schemas for Output SDK workflows?

Generate TypeScript types and Zod schemas for Output SDK workflows by running the type-generation tool against your schemas to produce ready-to-use definitions. It defines and exports workflow input, step input, and step output types for validation and runtime execution.

What is the best way to ensure type safety and validation for Output SDK workflow inputs?

Ensure type safety for Output SDK workflows by generating TypeScript definitions that mirror Zod schemas. This approach provides compile-time type checking and runtime validation simultaneously, reducing manual boilerplate and ensuring consistent input and output validation across projects.

Do I need to import zod from @outputai/core to use generated workflow types?

Yes, you need z imported from @outputai/core to use the generated workflow types. The tool requires this dependency to define and export WorkflowInput, StepInput, and StepOutput schemas that validate data during runtime execution.

Can I define optional fields and defaults when creating Zod schemas for Output SDK step inputs?

Yes, you can define optional fields, defaults, and validation describes when creating Zod schemas for Output SDK step inputs. The type-generation tool supports these common patterns to mirror schemas accurately for downstream project integration.

How does generating types from Zod schemas compare to manually defining TypeScript interfaces for SDK workflows?

Generating types from Zod schemas automates the creation of strongly-typed TypeScript definitions, ensuring schemas and types never drift apart. Unlike manual interface definitions, this approach guarantees consistent validation and reduces boilerplate across downstream projects.

Why are my WorkflowInput types not matching the runtime validation in my Output SDK project?

WorkflowInput types may not match runtime validation if TypeScript definitions and Zod schemas are manually maintained separately. Generating types directly from schemas ensures compile-time types accurately mirror runtime validation rules for step inputs and outputs.