Creating Cursor Rules

Cursor rules are .mdc files with YAML frontmatter and structured sections that codify your project's conventions for AI assistants. Create a `.cursor/rules` file defining your tech stack, code style, and architectural patterns so AI generates code consistent with your team's standards without constant manual correction.

Effective TypeScript Cursor rules specify your framework version, language configuration, component patterns (like functional components with named exports), and concrete code examples. Focus on architectural decisions and team-specific conventions rather than basic linter rules that tools already enforce.

Write Cursor rules when starting a new project, onboarding developers, or documenting existing coding standards. Rules are most valuable when you have established architectural patterns and coding conventions you want AI assistants to follow consistently across generated code.

Organize Cursor rules into logical sections by concern: Tech Stack (frameworks and language versions), Code Style (naming conventions and export patterns), and Rule Types (architectural patterns with examples). This structure helps AI assistants understand context and apply rules consistently across different coding scenarios.

Avoid including basic linter territory, vague guidelines without examples, and untested rules. Instead, test rules with AI to verify they produce expected code, identify gaps, and focus on specific architectural decisions and project-specific conventions that differentiate your codebase.

Yes. Cursor rules are framework-agnostic and work with Next.js, TypeScript, and any tech stack. Define your specific framework version, language features, and component patterns in the Tech Stack and Code Style sections so AI generates code following your project's conventions.