typescript-zod-tailwind-nextjs-cursorrules-prompt- — Cursor rule
Cursor coding standard for Next.js and TypeScript: enforces functional patterns, Zod validation, Shadcn UI, and desktop-first Tailwind CSS.
.cursor/rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-.mdcWhat typescript-zod-tailwind-nextjs-cursorrules-prompt- does
This rule guides Cursor when generating TypeScript code for Next.js applications. It enforces functional, declarative patterns while disallowing classes and TypeScript enums in favor of maps and interfaces. Source files follow a fixed structure: exported component at the top, followed by subcomponents, helper functions, static data, and types.
Styling relies on Shadcn UI, Radix, and Tailwind Aria with a desktop-first responsive design. The guide minimizes useEffect and setState usage, limits the 'use client' boundary, and isolates client components behind Suspense fallbacks. Expected errors inside Server Actions must be returned as values instead of throwing exceptions. Because classes and enums are banned, object-oriented code will break these conventions.
What it helps with
- enforce functional TypeScript interfaces over classes and enums
- implement form validation using Zod schemas
- restrict
'use client'directives and client-side hook usage - format Server Actions to return expected errors as values
Example prompts for the agent
- Build a login form component with Zod validation and a Server Action using Shadcn UI
- Sync this catalog filter state directly with URL search parameters
- Create a desktop-first profile card styled with Tailwind CSS and Radix
How to install typescript-zod-tailwind-nextjs-cursorrules-prompt-
Manually: put the files in place
.cursor/rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-.mdThe paths frontmatter field limits the files: move globs from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.github/instructions/typescript-zod-tailwind-nextjs-cursorrules-prompt-.instructions.mdThe applyTo field sets which files it applies to: move globs from the source into applyTo
Manually: put the files in place
.devin/rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-.mdManually: put the files in place
.clinerules/typescript-zod-tailwind-nextjs-cursorrules-prompt-.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about typescript-zod-tailwind-nextjs-cursorrules-prompt-
How to install typescript-zod-tailwind-nextjs-cursorrules-prompt- in Cursor?
Save the rule file to .cursor/rules/typescript-zod-tailwind-nextjs-cursorrules-prompt-.mdc in your project root.
What does this rule enforce?
It enforces functional TypeScript without classes or enums, desktop-first Tailwind CSS, Zod form validation, and server-first Next.js architecture.
How are errors handled according to this rule?
Expected errors are modeled as return values in Server Actions, while unexpected failures are caught by React Error Boundaries.
Source text
typescript-zod-tailwind-nextjs-cursorrules-prompt-.mdc · CC0-1.0
--- description: "Cursor rules for TypeScript development with Zod, Tailwind, and Next.js integration." globs: **/* alwaysApply: false --- # 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
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules