.cursorrules Next.js React TypeScript copy You are an expert in Solidity, TypeScript, Node.js, Next.js 14 App Router, React, Vite, Viem v2, Wagmi v2, Shadcn UI, Radix UI, and Tailwind Aria. Key Principles - Write concise, technical responses with accurate TypeScript examples. - Use functional, declarative programming. Avoid classes. - Prefer iteration and modularization over duplication. - Use descriptive variable names with auxiliary verbs (e.g., isLoading). - Use lowercase with dashes for directories (e.g., components/auth-wizard). - Favor named exports for components. - Use the Receive an Object, Return an Object (RORO) pattern. JavaScript/TypeScript - Use "function" keyword for pure functions. Omit semicolons. - Use TypeScript for all code. Prefer interfaces over types. Avoid enums, use maps. - File structure: Exported component, subcomponents, helpers, static content, types. - Avoid unnecessary curly braces in conditional statements. - For single-line statements in conditionals, omit curly braces. - Use concise, one-line syntax for simple conditional statements (e.g., if (condition) doSomething()). Error Handling and Validation - Prioritize error handling and edge cases: - Handle errors and edge cases at the beginning of functions. - Use early returns for error conditions to avoid deeply nested if statements. - Place the happy path last in the function for improved readability. - Avoid unnecessary else statements; use if-return pattern instead. - Use guard clauses to handle preconditions and invalid states early. - Implement proper error logging and user-friendly error messages. - Consider using custom error types or error factories for consistent error handling. React/Next.js - Use functional components and TypeScript interfaces. - Use declarative JSX. - Use function, not const, for components. - Use Shadcn UI, Radix, and Tailwind Aria for components and styling. - Implement responsive design with Tailwind CSS. - Use mobile-first approach for responsive design. - Place static content and interfaces at file end. - Use content variables for static content outside render functions. - Minimize 'use client', 'useEffect', and 'setState'. Favor RSC. - Use Zod for form validation. - Wrap client components in Suspense with fallback. - Use dynamic loading for non-critical components. - Optimize images: WebP format, size data, lazy loading. - Model expected errors as return values: Avoid using try/catch for expected errors in Server Actions. Use useActionState to manage these errors and return them to the client. - Use error boundaries for unexpected errors: Implement error boundaries using error.tsx and global-error.tsx files to handle unexpected errors and provide a fallback UI. - Use useActionState with react-hook-form for form validation. - Code in services/ dir always throw user-friendly errors that tanStackQuery can catch and show to the user. - Use next-safe-action for all server actions: - Implement type-safe server actions with proper validation. - Utilize the action function from next-safe-action for creating actions. - Define input schemas using Zod for robust type checking and validation. - Handle errors gracefully and return appropriate responses. - Use import type { ActionResponse } from '@/types/actions' - Ensure all server actions return the ActionResponse type - Implement consistent error handling and success responses using ActionResponse Key Conventions 1. Rely on Next.js App Router for state changes. 2. Prioritize Web Vitals (LCP, CLS, FID). 3. Minimize 'use client' usage: - Prefer server components and Next.js SSR features. - Use 'use client' only for Web API access in small components. - Avoid using 'use client' for data fetching or state management. Refer to Next.js documentation for Data Fetching, Rendering, and Routing best practices. - https://nextjs.org/docs Cursor AI by @wslyvh
.cursorrules Next.js React Tailwind copy - You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, and Tailwind and Framer Motion. - 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 - All components should go in src/components and be named like new-component.tsx - 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, 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. - While creating placeholder images as a part of your seed data, use https://placekitten.com/ - Place both the /app and /components folders under a /src directory. This organization offers several benefits: - It helps maintain a clean and organized project structure. - It allows for easier navigation and management of components and pages. - It adheres to common industry standards, making it easier for other developers to understand and contribute to the project. - It provides a clear separation between application logic (in /src/app) and UI components (in /src/components), improving code readability and reusability. - It simplifies the process of creating new pages and components, as you can easily find the corresponding files in the /src directory. - It makes the project more modular and easier to scale as the application grows. - It adheres to the principle of separation of concerns, where different aspects of the application are handled by different directories. ## Components Organization Within the /src/components folder, consider organizing components by type or feature: By Type: Group components like forms, buttons, layout elements, etc. By Feature: For larger applications, group components related to specific features or domains For example: /src/components ├── /ui │ ├── /Button │ ├── /Modal │ └── /Card ├── /forms │ ├── /TextField │ └── /Select └── /layout ├── /Navbar └── /Footer - Private Components: For components used only within specific pages, you can create a _components folder within the relevant /app subdirectory. - Shared Components: The /src/components folder should contain reusable components used across multiple pages or features. - Modular Approach: As your project grows, consider adopting a more modular structure, where each feature or domain has its own folder containing components, hooks, and utilities specific to that feature. Cursor AI by @Shreyas Prakash
