Enforce strict TypeScript development with runtime schemas and derived types.
npx skills add https://github.com/mintuz/claude-plugins --skill typescript-mintuz
Please help me install this Agent Skill. Skill: typescript Source: https://github.com/mintuz/claude-plugins/tree/main/plugins/typescript/skills Command: npx skills add https://github.com/mintuz/claude-plugins --skill typescript-mintuz
Type-safe TypeScript codebases can be hard to enforce without a consistent approach to schemas, immutability, and clear type contracts. This Skill provides guidelines to align on schema-first validation, derived types, branded types, and robust utility patterns to reduce runtime errors and improve maintainability.
Create a zod schema for a User, derive the TypeScript User type from the schema, and validate data at a trust boundary.
High-intent search queries and answers about installing and using this skill.
To derive TypeScript types from zod schemas, define your runtime schema first, then use utility types to infer the TypeScript type. This schema-first approach ensures your compile-time types automatically match your validation rules without manual synchronization.
Branded types create domain-safe identifiers by attaching a unique brand property to primitive types at compile time. This prevents accidental misuse of IDs across different API boundaries, ensuring a UserId cannot be passed where a ProductId is expected.
Schema-first TypeScript development requires a disciplined tsconfig with strict mode enabled. This enforces immutability patterns, readonly contracts, and strict type checking necessary for deriving types from schemas and maintaining type safety across trust boundaries.
Enforcing immutability in TypeScript involves using readonly types, branded types, and safe data transformation patterns. These approaches prevent mutation across API boundaries, ensuring data integrity and improving codebase maintainability without runtime overhead.
Validating data at API trust boundaries involves creating zod schemas for incoming data, deriving TypeScript types from those schemas, and validating data before processing. This schema-first approach ensures only correctly shaped data enters your internal system.
Schema-first TypeScript patterns require schema libraries like zod and a strict tsconfig setup. You should avoid this approach if your project lacks schema library dependencies or if your codebase cannot enforce the disciplined strict mode configuration required for readonly contracts and branded types.
reidemeister94Establish a four-phase TypeScript workflow with strict configs and Zod validation.
AZANIRGenerate realistic test data with fixtures, factories, and faker seeds.
g-bastianelliValidates TypeScript data with Zod schemas at trust boundaries.
H2OSLabsConverts Synnovator data schemas into OpenAPI 3.0 YAML or JSON specifications.
