typescript-nextjs-supabase-cursorrules-prompt-file — Cursor rule
A Cursor rule that keeps TypeScript work on Next.js App Router and Supabase consistent: server components first, Shadcn UI, Tailwind.
.cursor/rules/typescript-nextjs-supabase-cursorrules-prompt-file.mdcWhat typescript-nextjs-supabase-cursorrules-prompt-file does
The file loads into Cursor as a rule scoped to **/*, so it applies to every file in the project. Inside are conventions for the stack: TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI, Supabase, Tailwind and the Vercel AI SDK. The agent reads them before it starts writing.
The style section is specific. Functional components over classes, interfaces over types, const objects instead of enums, arrow functions, named exports, lowercase dashed directories. On performance it asks you to cut back on use client, useEffect and useState in favour of React Server Components, and to wrap client components in Suspense with a fallback. Data comes through the Supabase SDK, models through the schema builder, URL search state through nuqs.
One catch: alwaysApply is set to false, so the rule does not switch itself on. You have to enable it, or Cursor ignores the file. If your project is not on Next.js App Router or does not use Supabase, some advice will miss the mark — worth checking before you enable the whole thing instead of trimming the sections you do not need.
What it helps with
- keep TypeScript style consistent across a team without nitpicking every diff
- push the agent toward server components instead of client ones by default
- line up Supabase SDK queries and schema builder work in one codebase
- use Shadcn UI, Radix and Tailwind without mixing conventions
- spell out file and directory naming so generated code fits the repo
Example prompts for the agent
- Add a new sign-in form component following the project rules
- Rewrite this component as a server component instead of a client one
- Write the Supabase query for the orders list and wire it into the App Router
How to install typescript-nextjs-supabase-cursorrules-prompt-file
Manually: put the files in place
.cursor/rules/typescript-nextjs-supabase-cursorrules-prompt-file.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/typescript-nextjs-supabase-cursorrules-prompt-file.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-nextjs-supabase-cursorrules-prompt-file.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-nextjs-supabase-cursorrules-prompt-file.mdManually: put the files in place
.clinerules/typescript-nextjs-supabase-cursorrules-prompt-file.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about typescript-nextjs-supabase-cursorrules-prompt-file
How do I install typescript-nextjs-supabase-cursorrules-prompt-file in Cursor?
Create .cursor/rules/typescript-nextjs-supabase-cursorrules-prompt-file.mdc and paste the rule contents into it. Then enable it in Cursor settings yourself, since alwaysApply is false.
What does this rule do?
It hands the agent conventions for TypeScript, Next.js App Router, React, Supabase, Tailwind and the Vercel AI SDK: code style, naming, server component usage and database queries.
Does the rule turn on by itself once the file is added?
No. The file sets alwaysApply: false, so auto-apply is off and you have to activate the rule manually.
Source text
typescript-nextjs-supabase-cursorrules-prompt-file.mdc · CC0-1.0
--- description: "Cursor rules for TypeScript development with Next.js and Supabase integration." globs: **/* alwaysApply: false --- You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI, Supabase, Tailwind, and Vercel AI SDK. **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 const objects or as const assertions instead. - Use functional components with TypeScript interfaces. **Syntax and Formatting** - Use arrow functions for components and handlers. - 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 'useState'; favor React Server Components (RSC). - Wrap client components in Suspense with fallback. - Use dynamic loading for non-critical components. - Optimize images: use Next.js Image component, include size data, implement lazy loading. **Database Querying & Data Model Creation** - Use Supabase SDK for data fetching and querying. - For data model creation, use Supabase's schema builder. **Key Conventions** - Use 'nuqs' for URL search parameter state management. - Optimize Web Vitals (LCP, CLS, FID). - Limit 'use client': - Favor server components and Next.js SSR. - Use only for Web API access in small components. - Avoid for data fetching or state management. **Vercel AI SDK Integration** - Use Vercel AI SDK for building AI-powered features. - Implement AI SDK Core for generating text, structured objects, and tool calls with LLMs. - Utilize AI SDK UI hooks for building chat interfaces. - Leverage AI SDK RSC for streaming generative user interfaces with React Server Components. **Data Fetching and API Routes** - Use Next.js App Router conventions for data fetching and API routes. - Implement efficient caching and revalidation strategies using Next.js built-in features. - Use route handlers (route.ts) for API routes in the App Router. **Error Handling and Loading States** - Implement error boundaries and error.tsx files for error handling. - Use loading.tsx files for managing loading states. **SEO and Metadata** - Use Next.js 14's metadata API for SEO optimization. **Follow Next.js docs for Data Fetching, Rendering, and Routing.**
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules