omk-typescript-strict

What problem does it solve?

Inconsistent TypeScript settings lead to fragile code, hidden runtime bugs, and slow reviews caused by weak typing and unclear boundaries across full-stack frameworks.

Core Features & Use Cases

• Enforces strict TypeScript rules: assumes strict mode, avoids any and unsafe casts, mandates exported function return types, and promotes discriminated unions for state machines.
• Clarifies framework boundaries: keeps Next.js server/client separation explicit and validates route/search params instead of relying on unchecked values.
• Improves NestJS structure and safety: keeps controllers thin, places business logic in services, validates DTOs, and prevents leaking ORM entities as API responses.
• Review output standardization: provides a consistent review format covering type issues, boundary issues, unsafe casts, and suggested fixes.

Quick Start

Ask an AI to review your Next.js or NestJS codebase against OMK TypeScript strict-mode standards and produce a report using the sections Type issues, Boundary issues, Unsafe casts, and Suggested fix.