Cursor Rules

Cursor Rules solve a fundamental problem in AI-assisted development: getting AI to follow your project's specific conventions without repeating instructions every time.

What Goes in Cursor Rules

Effective rules typically include:

• Tech stack — Languages, frameworks, libraries
• Coding style — Naming conventions, file structure
• Patterns to use — State management, error handling
• Patterns to avoid — Anti-patterns, deprecated approaches
• Project context — What the app does, key concepts

Example Structure

# Project Context
This is a Next.js 15 application with TypeScript.
We use Tailwind CSS and Shadcn UI components.

# Coding Conventions
- Use functional components with hooks
- Prefer named exports over default exports
- Use 'type' instead of 'interface' for TypeScript
- Handle errors with try/catch and proper error types

# File Structure
- Components go in /components
- Server actions in /server
- Utilities in /lib

Why Rules Beat Repeated Prompts

Without rules, you might type "remember to use TypeScript" dozens of times per day. Rules:

1. Apply automatically to every interaction
2. Stay consistent across team members
3. Can be version controlled with your code
4. Evolve as your project standards change

Making Rules Effective

• Be specific but not overwhelming
• Include examples of preferred patterns
• Update rules when conventions change
• Share rules across similar projects