typescript zod tailwind nextjs cursorrules prompt
via PatrickJS/awesome-cursorrules
TypeScript, Zod validation, Tailwind CSS, and Next.js best practices for Cursor.
What is typescript zod tailwind nextjs cursorrules prompt ?
Establishes coding conventions for TypeScript development with Zod form validation, Tailwind CSS styling, and Next.js framework integration. Use this rule to enforce functional programming patterns, proper error handling, React Server Components, and performance optimization across your project.
- Write functional TypeScript with interfaces, Zod validation, and early error handling via guard clauses
- Structure components with named exports, descriptive variable names, and declarative JSX patterns
- Style with Tailwind CSS (desktop-first responsive design) and Shadcn/Radix/Aria component libraries
- Optimize performance by favoring React Server Components, minimizing useEffect, and using dynamic loading for non-critical components
- Manage state via URL search parameters and Server Actions; model expected errors as return values
- Implement image optimization (WebP, lazy loading, size data) and Web Vitals monitoring (LCP, CLS, FID)
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
Coding Style Guide
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
- Use Zod for form validation
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
Error Handling and Validation:
- Prioritize error handling: handle errors and edge cases early
- Use early returns and guard clauses
- Implement proper error logging and user-friendly messages
- Use Zod for form validation
- Model expected errors as return values in Server Actions
- Use error boundaries for unexpected errors
UI and Styling:
- Use Shadcn UI, Radix, and Tailwind Aria for components and styling
- Implement responsive design with Tailwind CSS; use a desktop-first approach
Performance Optimization:
- Minimize 'useEffect', and 'setState'; favor React Remix 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 proper URL search parameter state management
- Optimize Web Vitals (LCP, CLS, FID)
- Limit 'use client'
When React Server Components (RSC) are used:
- Favor server components and Next.js SSR
- Use only for Web API access in small components
- Avoid for data fetching or state management
Follow React Remix docs for Data Fetching, Rendering, and Routing
Follow Next.js docs for Data Fetching, Rendering, and Routing when Next JS is used instead of React Remix
Related rules
Senior full-stack TypeScript, React, Node.js guidance with clean architecture, testing, and WHY-oriented reasoning.
Quantitative factor research skills for designing, evaluating, and mining alpha factors in equities markets.
Android development with Jetpack Compose, clean architecture, and Material Design 3.
Angular development with Novo Elements UI library using standalone components.
Expert Angular 18 + TypeScript development with Jest, emphasizing clean code and performance.
Manage Kubernetes clusters, add-ons, stacks, and credentials via the Ankra CLI platform.