typescript-expert

Type-safe TypeScript prioritizes explicit types over `any`, uses discriminated unions and utility types to model domain logic precisely, and validates inputs while sanitizing outputs. This prevents runtime errors and makes code intent clear to maintainers.

Organize TypeScript projects with simple, readable modules following consistent naming conventions. Document public APIs with JSDoc, maintain project-specific testing and lifecycle patterns, and apply security practices like avoiding dynamic code execution throughout the codebase.

Refactoring TypeScript code means replacing loose typing with strong type constraints, simplifying module boundaries, ensuring input validation and output sanitization, and aligning naming and documentation with project conventions. This improves security and readability.

Security-focused TypeScript patterns include strict input validation, output sanitization, avoiding dynamic code execution, and leveraging the type system to prevent entire classes of bugs. Pair these with comprehensive test coverage aligned to project standards.

Discriminated unions model mutually exclusive states precisely and enable exhaustiveness checking at compile time. Utility types (`Omit`, `Pick`, `Readonly`) reduce duplication and enforce immutability constraints, making type relationships explicit and maintainable.

Yes, document public TypeScript APIs with JSDoc comments to clarify intent, parameters, and return values for maintainers and tools. Follow your project's conventions for naming, testing lifecycles, and documentation depth to keep documentation in sync with code.