What problem does it solve? Complex typing problems in a large TypeScript monorepo—generics, conditional types, inference failures, and untyped boundaries—slow down development and let runtime errors slip through. This Skill provides expert-level guidance for designing type-safe architectures across shared packages, NestJS APIs, and Next.js apps when standard TypeScript help is not enough. ## Core Features & Use Cases - Advanced Type Design: Builds generics, conditional types, mapped types, and custom utility types with semantic naming and proper constraints. - Monorepo-Wide Type Safety: Applies strict typing conventions across @iwana/shared DTOs, TypeORM entities, React CVA components, NestJS decorators, and Next.js Server/Client Components. - Review Checklist Enforcement: Flags unjustified any, missing return types, non-strict tsconfigs, and missing class-validator or Zod validation at boundaries. - Use Case: When a generic repository method like runInTenantSchema<T> loses type inference across the NestJS API, use this Skill to redesign the generics so tenant-scoped queries stay fully typed end to end. ## Quick Start Ask the assistant to review or redesign the TypeScript types for a specific service, DTO, or shared package in the iWana neXt repo.
