typescript-best-practices

TypeScript type safety is enforced by preferring `unknown` over `any`, using type narrowing and typed guards, and avoiding risky non-null assertions. This approach guides you toward stronger type safety that prevents common bugs and runtime failures.

The best way to handle errors in TypeScript is adopting typed `Result`-style flows and structured error types with specific codes. This ensures predictable recovery paths and prevents unhandled runtime failures across your modules.

Yes, Deno supports deterministic TypeScript analysis workflows by running a static analyzer to detect anti-patterns across files or directories. This workflow applies strict type-safety rules to discourage known anti-patterns and ensure architecture consistency.

Generating TypeScript types from JSON inputs uses scaffolding workflows to produce well-structured modules with explicit exports. It supports creating single-concept modules with optional tests to maintain architecture-consistent APIs for any project scope.

Non-null assertions in TypeScript bypass compiler safety checks, creating runtime failure risks. The skill discourages known anti-patterns like `!` assertions and `@ts-ignore`, guiding you toward safer type narrowing and typed guards for robust error handling.