typescript nodejs nextjs app cursorrules prompt fi
via PatrickJS/awesome-cursorrules
TypeScript/Node.js/Next.js App Router development guide with React, Shadcn UI, and Tailwind best practices.
What is typescript nodejs nextjs app cursorrules prompt fi?
This rule establishes coding standards and architectural patterns for TypeScript-based Next.js applications using the App Router. It covers naming conventions, component structure, performance optimization with React Server Components, and UI library preferences (Shadcn, Radix, Tailwind). Use it to maintain consistency across a modern full-stack Next.js project.
- Enforces TypeScript interfaces, functional components, and declarative JSX patterns
- Specifies directory naming (lowercase-dashes) and file structure conventions
- Prioritizes React Server Components and minimizes client-side state management
- Guides responsive design with Tailwind CSS using mobile-first approach
- Recommends Shadcn UI and Radix UI for component libraries
- Optimizes performance via dynamic loading, image optimization (WebP), and Web Vitals focus
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 and Tailwind.
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.
Please write me a web application in this mentioned style for an app with the following features:
please install all necessary npm packages first at the end the app should fully work and run in dev mode it will be a notes app a entry where you can add a new note a list of all notes a detail page for each note a edit page for each note a delete button for each note please also add a search field to the list of notes please also add a filter field to the list of notes please also add a sort field to the list of notes please also add a pagination to the list of notes please also add a loading state to the list of notes please also add an error state to the list of notes please add a drag and drop feature to the list of notes
Related rules
TypeScript, Next.js, React, and Tailwind best practices with Shadcn UI and Radix components.
TypeScript, Node.js, React, Vite, TanStack Query/Router, and Tailwind development guide.
TypeScript React development with functional components and strict typing.
TypeScript, React, Next.js, and Cloudflare development patterns with Shadcn UI and DrizzleORM.
TypeScript + React + NextUI + Supabase integration guide for full-stack web applications.
TypeScript + shadcn/ui + Next.js development conventions with RSC-first patterns and Tailwind styling.
