typescript-coding-engine

Check the TypeScript toolchain and quality-gate side of a problem before applying fixes

Check the type-system side of a TypeScript problem before applying fixes

Prime TypeScript foundations before implementation or review

Prime TypeScript tooling and quality surfaces before changing toolchain or standards

Choose the correct TypeScript runtime-validation path before implementation

Choose the correct TypeScript state or structure pattern before architecture or state work

Review TypeScript interop boundaries across Rust bindings, WASM bridges, Node native addons, and frontend runtime bridges. Trigger keywords: interop, wasm, ts-rs, tsify, napi-rs, bridge, tauri, bindings.

Review TypeScript architecture choices across layering, state management, config posture, modularity, and framework-independent structure. Trigger keywords: architecture, structure, tsconfig, state, modules, layering, monorepo.

Audit TypeScript toolchain posture including tsconfig, linting, testing, CI quality gates, and strictness discipline. Trigger keywords: tsconfig, eslint, prettier, vitest, quality gate, ci, strict mode.

Diagnose TypeScript type-system problems before patching symptoms. Trigger keywords: type error, generic, inference, narrowing, overload, any, as const, mapped type, conditional type.

Use when the task is about TypeScript project structure, layering, modularity, state-pattern selection, shared-core boundaries, or architecture-level trade-offs rather than local typing details.

Use when the task needs TypeScript foundations: strict typing, widening vs narrowing, baseline type-system behavior, or first-line mental models.

Use when the task is fundamentally about generics, inference, narrowing precision, overload selection, or preserving type information through APIs.

Use when the task involves Rust/TS type sharing, WASM/TS bridges, Tauri boundaries, generated contracts, or TypeScript-facing cross-language ownership questions.

Use when the task involves trust boundaries, schema posture, parsing external input, IPC/config/storage validation, or deciding when TypeScript's compile-time guarantees are not enough.

Use when the task involves TypeScript testing strategy, type tests, runtime tests, environment/framework test boundaries, CI confidence, or deciding what kind of proof the system actually needs.

Use when the task involves tsconfig strictness, linting, formatting, CI quality gates, testing posture, or broader TypeScript code quality governance.

Use when the task involves conditional types, mapped types, template literal types, infer patterns, opaque or brand types, or advanced type-level composition.

3 hooks across 3 events