Define TypeScript subsystems with runtime schemas and strict compiler settings.
npx skills add https://github.com/usurobor/cnos --skill typescript-usurobor
Please help me install this Agent Skill. Skill: typescript Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.eng/skills/eng/typescript Command: npx skills add https://github.com/usurobor/cnos --skill typescript-usurobor
Type-checking and runtime behavior often diverge; this skill ensures TypeScript code stays aligned with what runs at runtime, reducing drift.
Define a runtime model, a type model, and boundary validation for your TS subsystem and enable strict compiler settings to align runtime truth with types.
High-intent search queries and answers about installing and using this skill.
To keep TypeScript types in sync with runtime behavior, define runtime schemas for external input and enforce strict compiler settings. This reduces drift between static type models and actual execution across CLIs, services, and libraries.
Validating external input boundaries in TypeScript requires explicit runtime schemas to prevent unchecked data from entering the system. Discriminated unions and branded primitives further prevent subtle type confusion across module surfaces.
You need discriminated unions and branded primitives in TypeScript when preventing subtle type confusion across module surfaces. They ensure that distinct data types remain explicitly separated, maintaining stable APIs and clear module boundaries.
To set up a TypeScript subsystem with strict runtime validation, define a runtime model, a type model, and boundary validation. Enable strict compiler settings to align runtime truth with types and establish explicit async and error policies.
Yes, TypeScript runtime validation applies to browser and Node applications, alongside CLIs, services, tooling, and registries. It ensures runtime and type alignment matters across any environment where external boundaries must be checked.
TypeScript type models drift from runtime behavior when external boundaries lack explicit schemas and compiler settings are not strict. Defining explicit error policies and validating unchecked input prevents this divergence.
oborchersEnforce strict TypeScript type safety with Zod runtime validation.
calcosmicEnforce Node.js server-side best practices for error handling and async patterns.
potetoEnforce type-safe patterns in TypeScript projects with discriminated unions and type guards.
zapabobReview TypeScript and JavaScript code for type safety and best practices.
