tdsk-admin

Add the route path to the ERoutePath enum in src/types/routes.types.ts, register it in Routes.tsx using the SuspensePage helper for lazy loading, and create a loader in loaders.ts using criticalFetch or safeFetch. Pages must use default exports.

The dashboard uses a three-layer Jotai design: atom files define state, accessors.ts provides imperative get/set/reset functions for use outside React, and selectors.ts exposes useRecState and useDerivedState hooks. API services cache responses via TanStack Query while actions sync results into Jotai atoms.

API actions in actions/<domain>/api/ are async functions that call a service, update Jotai state, and return the response. Local actions in actions/<domain>/local/ are synchronous functions that directly mutate Jotai state, and API actions delegate to them after successful responses.

Yes, authentication uses Neon Auth via @neondatabase/neon-js with social OAuth providers including GitHub, GitLab, Google, and Vercel, plus an email login form. Providers are configured through the TDSK_AUTH_PROVIDERS environment variable.

Loaders using criticalFetch throw on error, which triggers the route's errorElement boundary. Use safeFetch instead when the data is optional, since it returns undefined on failure without breaking the route render.