This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
pnpm dev- Start development server on port 3000pnpm build- Build for productionpnpm serve- Preview production buildpnpm test- Run tests with Vitest
pnpx shadcn@latest add <component>- Add new Shadcn components (use latest version)
This is a TanStack Start application - a type-safe, client-first, full-stack React framework built on top of:
- TanStack Router: File-based routing with type-safe navigation
- TanStack Query: Server state management with SSR integration
- React 19: Latest React with concurrent features
- Vite: Build tool and dev server
- TypeScript: Strict type checking enabled
- Tailwind CSS v4: Utility-first styling with CSS variables
src/routes/- File-based routes (auto-generatesrouteTree.gen.ts)src/components/- Reusable React componentssrc/integrations/tanstack-query/- Query client setup and providerssrc/lib/utils.ts- Utility functions (includes clsx/tailwind-merge)src/utils/seo.ts- SEO helper functions- Path aliases:
@/*maps tosrc/*
Router Setup: The router is created via getRouter() in src/router.tsx which integrates TanStack Query context and SSR. Routes are auto-generated from the file system.
Query Integration: TanStack Query is pre-configured with SSR support through setupRouterSsrQueryIntegration. The query client is accessible in route contexts.
Root Layout: src/routes/__root.tsx defines the HTML document structure, includes devtools, and provides navigation links. It uses createRootRouteWithContext for type-safe context passing.
Styling: Uses Tailwind CSS v4 with the Vite plugin. Shadcn components are configured with "new-york" style, Zinc base color, and CSS variables enabled.
TypeScript: Strict mode with additional linting rules (noUnusedLocals, noUnusedParameters, etc.). Uses modern ESNext module resolution.
- Demo files (prefixed with
demo) can be safely deleted - The project uses pnpm as the package manager
- Devtools are included for both Router and Query in development
- Routes support loaders, error boundaries, and not-found components
- File-based routing automatically generates type-safe route definitions