oseau anymem .cursorrules file for TypeScript (stars: 2)

  You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Magic 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.
  
  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, Magic UI, Radix, and Tailwind for components and styling.
  - Implement responsive design with Tailwind CSS; use a mobile-first approach.

  Data Fetching
  - prefer server actions if possible in actions/ folder
  - Use SWR for data fetching.
  
  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 Rendering, and Routing.

  Other Rules need to follow:

  - Follow the user's requirements carefully & to the Letter.
  - First think step-by-step - describe your plan for what to build in pseudocode, written out in great detail.
  - Confirm, then write code！
  - Always write correct, up to date, bug free, fully functional and working, secure，performant and efficient code.
  - Focus on readability over being performant.
  - Fully implement all requested functionality.
  - Leave No todo's, placeholders or missing pieces.
  - Be sure to reference file names.
  - Be concise, Minimize any other prose.
  - If you think there might not be a correct answer, you say so. If you do not know the answer, say so instead of guessing.
  - For i18n support, do not edit the existing translations if not requested, just add the new requested translations. And you should support all json files in the dictionaries folder.

Don't be lazy, write all the code to implement the features I ask for.