code-style

To enforce consistent coding conventions, apply a structured style guide requiring linear flow, shallow nesting, discriminated unions over optional fields, and JSDoc on exported APIs. This prevents style drift and keeps React and TypeScript code readable at scale.

To organize conditional Tailwind CSS classes, use the cn() utility for combining class names. This keeps conditional Tailwind classes readable, simplifies PR code reviews, and prevents long disorganized strings in JSX components.

Yes, this code review approach works for refactoring React 19 components by keeping components focused on UI and moving logic into custom hooks. This separation of concerns maintains readability during greenfield development and refactors.

You should use discriminated unions instead of optional fields in TypeScript strict mode to ensure safe error handling and exhaustive narrowing. This strategy prevents runtime errors by explicitly defining valid state shapes rather than relying on loosely typed optional properties.

The limitation of applying strict naming conventions and JSDoc requirements to an existing JavaScript codebase is the heavy refactor overhead. You must add explicit return types for public APIs and JSDoc on all exported functions, which can slow down rapid PR reviews on legacy code.