code-style

TypeScript naming conventions enforce consistency through file, component, and variable standards: use kebab-case for filenames, PascalCase for components and types, camelCase for variables, UPPER_CASE for constants, and 'use' prefix for hooks. Configure linting rules to validate these patterns automatically across your codebase.

Structure TypeScript components functionally with explicit return types, enable noUncheckedIndexedAccess for strict safety, use 'use client' directive for client components, organize exports consistently, and place helper functions and types within the same module. This ensures type safety and maintainability across your Oak AI application.

Error handling in TypeScript requires always awaiting promises, rethrowing errors with cause to preserve the original stack trace, structuring errors with context, and providing user-friendly messages. This pattern maintains debugging clarity while delivering appropriate feedback to users.

Organize tRPC through router structure, procedure definitions, and middleware patterns aligned with your project's kebab-case file naming and camelCase identifier conventions. This ensures consistent API routing while maintaining the coding standards enforced across your application.

Testing patterns include unit tests with Jest, component tests with React Testing Library for UI validation, and E2E tests with Playwright for full workflows. These standardized patterns ensure comprehensive coverage and consistency with your TypeScript coding standards.

Yes. Zustand stores integrate with strict TypeScript through explicit typing, supporting useState, useReducer, and TanStack Query alongside Zustand for state management. This creates consistent, type-safe state handling aligned with your project's conventions.