pp-typescript

Standardize TypeScript authoring conventions by applying unified rules for naming, type constructs, file layout, and test placement. This eliminates inconsistency and technical debt by enforcing strict typing, explicit return types, and named exports across all .ts and .tsx files.

Best practices for TypeScript file structure include top-down file ordering and colocated behavioral tests. Files should use strict typing, named exports, branded types, and discriminated unions to align with project architecture and maintain clear module boundaries.

Refactor existing TypeScript code by aligning only the specific lines you are modifying with project standards. This context-aware approach prevents unnecessary churn by updating naming conventions and type constructs only where you are actively touching the code.

Yes, these TypeScript coding standards apply to all .ts and .tsx file generation, modification, and refactoring tasks. The conventions ensure strict typing and explicit return types are enforced consistently across both standard TypeScript and React JSX environments.

Use branded types and discriminated unions when adding new services or modules to ensure robust type safety. These standardized type constructs satisfy strict typing requirements and help align new implementations with your existing project architecture seamlessly.