mauricedb sci-fi-cinema-24 .cursorrules file for TypeScript (stars: 1)

You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.

Code Style and Structure

- Write concise, technical TypeScript code with accurate examples.
- Use functional and declarative programming patterns; avoid classes.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
- Structure files: exported component, subcomponents, helpers, static content, types.
- Use the ./src directory for all source code.

Naming Conventions

- Use lowercase with dashes for directories (e.g., components/auth-wizard).
- Favor named exports for components.

TypeScript Usage

- Use TypeScript for all code; prefer interfaces over types.
- Avoid enums; use maps instead.
- Use functional components with TypeScript interfaces.

Syntax and Formatting

- Use the "function" keyword for pure functions.
- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
- Use declarative JSX.

UI and Styling

- Use Shadcn UI, Radix, and Tailwind for components and styling.
- Implement responsive design with Tailwind CSS; use a mobile-first approach.

Performance Optimization

- Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).
- Wrap client components in Suspense with fallback.
- Use dynamic loading for non-critical components.
- Optimize images: use WebP format, include size data, implement lazy loading.

Key Conventions

- Use 'nuqs' for URL search parameter state management.
- Optimize Web Vitals (LCP, CLS, FID).
- Limit 'use client':
  - Favor server components and Next.js SSR.
  - Use only for Web API access in small components.
  - Avoid for data fetching or state management.

Follow Next.js docs for Data Fetching, Rendering, and Routing.

Database and ORM

- Use Prisma as the primary ORM for database operations([1](https://www.prisma.io/docs/getting-started/quickstart)).
- Follow singleton pattern for PrismaClient instantiation:
  - Create lib/prisma.ts for client export
  - Use single instance across server components
- Prefer Prisma schema migrations over direct SQL:
  - Run migrations in development with `prisma migrate dev`
  - Deploy with `prisma migrate deploy`
- Structure database queries:
  - Keep queries in separate service files (e.g., services/user.ts)
  - Use strong typing with Prisma-generated types
  - Implement repository pattern for complex queries

Database Best Practices

- Use server components for database operations
- Implement proper error handling and type safety:
  - Wrap Prisma operations in try/catch blocks
  - Use Zod for input validation
  - Handle Prisma errors explicitly
- Optimize queries:
  - Select only needed fields
  - Use includes judiciously
  - Implement pagination for large datasets
- Cache frequently accessed data:
  - Utilize Next.js cache mechanisms
  - Implement proper cache invalidation