type-driven-zod-boundaries

You validate external input at module boundaries by pairing plain TypeScript domain types with Zod boundary schemas. This enforces type-safe boundary contracts, ensuring a clean separation where business logic lives in entities while boundaries validate structure.

Separating business rules from input validation in TypeScript is best achieved by defining plain domain types for entities and using Zod boundary schemas at module edges. Boundary schemas validate external data, while entities retain business logic.

You create operation-specific schemas for Create and Update flows by defining distinct Zod boundary schemas for each operation. This provides structured input for use cases without duplicating fields across your domain types.

Yes, this type-driven boundary schema approach works with React Hook Form. The skill provides form integration guidance and sample schemas to support UI frameworks, allowing you to derive form types directly from your Zod boundary schemas.

Yes, you need Zod v4 to implement type-driven boundary schemas. The skill requires Zod v4 alongside TypeScript domain types to derive boundary types automatically with z.infer and validate inputs at feature boundaries.

You handle schema evolution with Zod boundary schemas by following the provided schema evolution guidance, which covers additive changes and versioned migrations to ensure backwards compatibility as your feature boundaries expand.