Enforce API contracts with Zod and OpenAPI schemas for REST and RPC endpoints.
npx skills add https://github.com/imehr/vet --skill api-validation
Please help me install this Agent Skill. Skill: api-validation Source: https://github.com/imehr/vet/tree/main/.claude/skills/api-validation Command: npx skills add https://github.com/imehr/vet --skill api-validation
This skill ensures API contracts stay in sync by defining inputs and outputs with type-safe schemas, reducing runtime errors and mismatches between client and server.
Use Case: When designing an API, apply contract-driven design to guarantee end-to-end type safety and robust error handling.
High-intent search queries and answers about installing and using this skill.
To enforce API contracts and prevent type drift, define input and output DTOs using Zod and OpenAPI schemas. This establishes a single source of truth, ensuring runtime validation and parsing at API boundaries before transforming data into trusted domain types.
Yes, you can integrate Zod and OpenAPI validation with tRPC for end-to-end type safety. This skill applies contract-driven design to both REST and RPC endpoints, guaranteeing consistent data shapes and robust error handling across your stack.
The best way to validate outgoing API responses is to wire your endpoints with response schemas. Validating outgoing data against a defined OpenAPI or Zod schema enforces consistent API shapes and prevents unexpected client-side runtime errors.
Yes, contract-driven API design requires Zod and OpenAPI tooling to be available in your project. These dependencies are necessary to define type-safe schemas, generate OpenAPI docs and TypeScript types, and apply runtime validation.
You need runtime validation at API boundaries because TypeScript only checks types at compile time. Applying Zod schemas at the boundary validates incoming data at runtime, transforming untrusted external payloads into verified domain types safely.
Yes, you can use this schema validation approach with Express and Next.js. It generates OpenAPI documentation and TypeScript types while wiring validators to endpoints, ensuring robust error handling across different web frameworks.
Serg28Create OpenAPI 3.1 YAML specifications with endpoints, schemas, and security.
pr-pmReplace TypeScript any types with interfaces, type guards, and generic constraints.
abcnutsConvert natural language API specifications into endpoints for Next.js, tRPC, and Express.
litestar-orgConfigure Litestar DTOs and validate OpenAPI schemas for REST APIs.
