PluginBench
Rule

typescript react nextjs cloudflare cursorrules pro

via PatrickJS/awesome-cursorrules

TypeScript, React, Next.js, and Cloudflare development patterns with Shadcn UI and DrizzleORM.

What is typescript react nextjs cloudflare cursorrules pro?

Comprehensive guide for building full-stack applications with TypeScript, React, and Next.js on Cloudflare infrastructure. Covers code style, UI component libraries, performance optimization, and Cloudflare primitives like D1, KV, R2, and AI inference.

  • Enforces TypeScript best practices with functional programming patterns and descriptive naming conventions
  • Guides React Server Component usage and minimizes client-side overhead with Suspense and dynamic loading
  • Provides Shadcn UI, Radix UI, and Tailwind CSS styling patterns with mobile-first responsive design
  • Recommends Cloudflare developer tools (D1, KV, R2, AI) and wrangler CLI commands for serverless infrastructure
  • Optimizes Web Vitals and image performance using WebP format and lazy loading
  • Structures Next.js App Router projects with modular file organization and named exports

Applies to

File patterns this rule matches.

**/*
Rule definition (reference)

Source of truth, from the repository.

You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI, Tailwind CSS and DrizzleORM. You are also excellent at Cloudflare developer tools like D1 serverless database and KV. You can suggest usage of new tools (changes in wrangler.toml file) to add more primitives like:

R2: File storage KV: Key-value storage AI: AI multimodal inference others primitives in wrangler.toml

In the terminal, you are also an expert at suggesting wrangler commands.

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.

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, Radix, 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': Follow Next.js docs for Data Fetching, Rendering, and Routing.

Related rules

TypeScript + React + NextUI + Supabase integration guide for full-stack web applications.

**/*
41k
via PatrickJS/awesome-cursorrules

TypeScript + shadcn/ui + Next.js development conventions with RSC-first patterns and Tailwind styling.

**/*
41k
via PatrickJS/awesome-cursorrules

TypeScript, Vite, and Tailwind best practices with Vue 3 Composition API and DaisyUI.

**/*
41k
via PatrickJS/awesome-cursorrules

TypeScript and Vue.js development conventions and best practices.

**/*
41k
via PatrickJS/awesome-cursorrules

TypeScript, Zod, Tailwind, and Next.js coding standards for Cursor.

**/*
41k
via PatrickJS/awesome-cursorrules

TYPO3 CMS extension development with modern PHP 8.3+, PSR standards, and best practices.

**/*
41k
via PatrickJS/awesome-cursorrules