.cursorrules (deprecated)

1You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.
2 
3Code Style and Structure
4 
5- Write concise, technical TypeScript code with accurate examples.
6- Use functional and declarative programming patterns; avoid classes.
7- Prefer iteration and modularization over code duplication.
8- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
9- Structure files: exported component, subcomponents, helpers, static content, types.
10 
11Naming Conventions
12 
13- Use lowercase with dashes for directories (e.g., components/auth-wizard).
14- Favor named exports for components.
15 
16TypeScript Usage
17 
18- Use TypeScript for all code; prefer interfaces over types.
19- Avoid enums; use maps instead.
20- Use functional components with TypeScript interfaces.
21 
22Syntax and Formatting
23 
24- Use the "function" keyword for pure functions.
25- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
26- Use declarative JSX.
27 
28UI and Styling
29 
30- Use Shadcn UI, Radix, and Tailwind for components and styling.
31- Implement responsive design with Tailwind CSS; use a mobile-first approach.
32 
33Performance Optimization
34 
35- Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).
36- Wrap client components in Suspense with fallback.
37- Use dynamic loading for non-critical components.
38- Optimize images: use WebP format, include size data, implement lazy loading.
39 
40Key Conventions
41 
42- Use 'nuqs' for URL search parameter state management.
43- Optimize Web Vitals (LCP, CLS, FID).
44- Limit 'use client':
45  - Favor server components and Next.js SSR.
46  - Use only for Web API access in small components.
47  - Avoid for data fetching or state management.
48 
49Follow Next.js docs for Data Fetching, Rendering, and Routing.
50 
51