react-best-practices

Use contracts.ts to define stable API types and wire all calls through ENDPOINTS, ensuring TypeScript catches type mismatches at build time. This pattern centralizes type definitions and prevents integration drift across components.

Use TanStack Query for server state and data fetching, and Zustand for client-side UI state. This separation reduces boilerplate, keeps data fetching logic testable, and avoids the complexity of libraries like Redux or MobX.

Combine shadcn/ui components with Radix UI for accessible primitives and Tailwind CSS with semantic colors and dark mode support. This creates uniform styling across domains and reduces custom CSS maintenance.

Yes. React Hook Form paired with Zod provides runtime and compile-time validation, reducing form bugs and boilerplate. Define Zod schemas alongside your contracts.ts for end-to-end type safety.

Zustand is simpler to set up, requires less boilerplate, and integrates cleanly with TanStack Query for server state. It reduces cognitive overhead while maintaining predictable state patterns aligned with EUCORA standards.

Avoid Redux, Next.js, and MobX. This Skill enforces TanStack Query for server state, Zustand for UI state, and standard React patterns to maintain consistency and reduce incompatible dependencies across projects.