What is a .cursorrules file?

A .cursorrules file is a configuration file placed in your project root that tells Cursor AI how to write and review code in your project. It sets project-specific conventions, code style, and AI behavior guidelines.

Where do I put the .cursorrules file?

Place it in the root directory of your project (same level as package.json or pyproject.toml). Cursor AI reads it automatically when you open the project.

What's the difference between this and cursor-rules-generator?

The cursor-rules-generator creates rules based on your existing codebase analysis. This builder creates rules from scratch using guided steps — useful for new projects or standardizing rules across a team.

Cursor Rules Builder Online — .cursorrules (Free, No Upload)

Export format

Preview

55 lines · 2.0 KB

↓ .cursorrules

# Cursor Rules — Next.js 14+ with App Router

## Project
You are working on a Next.js 14+ with App Router project.
Use TypeScript throughout. Prefer strict mode types.
Use Next.js App Router conventions. Server Components by default; add 'use client' only when needed.
Prefer Server Actions for mutations over API routes.
Use Tailwind CSS for styling. Avoid inline styles and custom CSS unless necessary.
Use shadcn/ui for UI components. Follow its component patterns and theming conventions.

## Database
Use Prisma for database access. Always use transactions for multi-step writes.

## State Management
Use Zustand for global state. Keep stores small and focused; prefer slices.

## API / Backend
Use Next.js Server Actions for mutations. Validate all inputs with Zod.

## Authentication
Use NextAuth.js for authentication. Always protect server-side routes with session checks.
Use middleware to protect routes. Check session in Server Components with getServerSession.

## Code Style
- Indentation: 2 spaces
- Quotes: double quotes (")
- Semicolons: required
- Prefer const over let; never use var
- Use explicit return types on exported functions
- Prefer interface over type for object shapes
- All code must pass ESLint with no warnings
- Format with Prettier before committing

## Naming Conventions
- Components: PascalCase
- Files: kebab-case
- CSS classes: Tailwind

## Testing
- Use Vitest for tests
- Follow AAA pattern: Arrange, Act, Assert
- Name tests descriptively: 'should return error when input is empty'
- Test behavior, not implementation

## Deployment
- Deployment target: Vercel
- Use Vercel Edge Runtime for latency-sensitive routes

## AI Behavior Rules
- Prefer small, focused functions (single responsibility)
- Always write self-documenting code; add comments only for non-obvious logic
- Never use `any` or `unknown` without explicit type justification
- Prefer early returns over deeply nested conditions
- Always handle errors explicitly — no empty catch blocks
- Use environment variables for all secrets; never hardcode credentials

🔒 Runs in your browser · No uploads · Your data never leaves your device

How to use

Pick a preset or configure manually
Click a quick-start preset like 'Next.js 14 + TS + Tailwind' to populate all fields, or configure from scratch using the step-by-step options.
Select your project type
Choose Next.js, React, Node.js, Python, Vue, SvelteKit, or Other to set the foundational rules.
Choose your tech stack
Toggle the libraries and tools you use — TypeScript, Tailwind, Prisma, Zustand, and more. Each selection adds relevant AI guidance.
Download or copy
Copy the generated .cursorrules to your clipboard or download it directly. Place the file in your project root.

Common use cases

Starting a new project with consistent AI rules — Pick a preset for your stack to instantly populate .cursorrules with relevant conventions before writing any code.
Standardizing rules across a team — Build and share a .cursorrules file so all team members get consistent AI assistance in their Cursor IDE.

Examples

Next.js 14 + TypeScript
Full-stack Next.js with App Router, TypeScript strict mode, Tailwind CSS, ESLint, and Prettier.
Output
```
.cursorrules with App Router conventions, TypeScript rules, and formatting preferences
```

Frequently asked questions

What is a .cursorrules file?: A .cursorrules file is a configuration file placed in your project root that tells Cursor AI how to write and review code in your project. It sets project-specific conventions, code style, and AI behavior guidelines.
Where do I put the .cursorrules file?: Place it in the root directory of your project (same level as package.json or pyproject.toml). Cursor AI reads it automatically when you open the project.
What's the difference between this and cursor-rules-generator?: The cursor-rules-generator creates rules based on your existing codebase analysis. This builder creates rules from scratch using guided steps — useful for new projects or standardizing rules across a team.

Key concepts

.cursorrules: A plain text configuration file that tells Cursor AI how to generate and review code in a specific project.
Preset: A predefined configuration template for common stacks (e.g., Next.js + TypeScript + Tailwind) that populates all rules automatically.

You might find these useful too.

Cursor Rules Builder tool

How to use

Pick a preset or configure manually

Select your project type

Choose your tech stack

Download or copy

Common use cases

Examples

Next.js 14 + TypeScript

Frequently asked questions

Key concepts

Related tools

More ai tools