typescript zod tailwind nextjs cursorrules prompt
via PatrickJS/awesome-cursorrules
TypeScript, Zod, Tailwind, and Next.js coding standards for Cursor.
What is typescript zod tailwind nextjs cursorrules prompt ?
Establishes conventions for TypeScript development with Zod validation, Tailwind styling, and Next.js integration. Use this rule to enforce functional programming patterns, server-side rendering best practices, and performance optimization across your project.
- Enforce TypeScript interfaces, functional components, and Zod-based form validation
- Establish naming conventions: lowercase-dash directories, named component exports, descriptive variable names with auxiliary verbs
- Implement error handling with early returns, guard clauses, and user-friendly messages; model expected errors as return values in Server Actions
- Optimize performance by favoring React Server Components, minimizing useEffect, using Suspense boundaries, and dynamic loading for non-critical components
- Apply Tailwind CSS with desktop-first responsive design using Shadcn UI and Radix components
- Structure files with exported component, subcomponents, helpers, static content, and types in consistent order
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
TYPO3 CMS extension development with modern PHP 8.3+, PSR standards, and best practices.
Swift UIKit development guidelines emphasizing clean architecture, Auto Layout with SnapKit, and programmatic UI composition.
C# guidance for Unity tower defense game with Ringcon controller integration.
Best practices for Vercel deployments, serverless functions, Edge Runtime, and CI/CD configuration.
Expert guidance for deploying serverless applications on Vercel with Edge Runtime, middleware, and production best practices.
Expert Vitest unit testing guidance with TypeScript support and dependency mocking.
