Cursor Rules Directory

Feature Comparison

Directory Structure

Keep rules close to the repository and name files by the workflow or area they govern.

.cursor/
  rules/
    project.mdc
    frontend.mdc
    backend.mdc
    tests.mdc
    review.mdc

Project Baseline Template

Use this as the first rule in a new repository, then customize the commands to match the actual package manager.

---
description: Project baseline rules
globs: ["**/*"]
---
Use the existing architecture before adding new abstractions.
Prefer small, reviewable diffs.
Run the narrowest relevant test first, then run the full build before release.
Do not edit generated files unless the task explicitly requires it.

Frontend Template

Scope frontend rules to app and component files so Cursor sees them when it edits UI code.

---
description: Frontend rules
globs: ["app/**/*", "components/**/*", "src/**/*.{tsx,jsx,css}"]
---
Use existing components and design tokens before creating new patterns.
Keep interactive states accessible.
Check mobile layout for text wrapping and overflow.
Run npm run build after route or component changes.

Backend Template

Backend rules should name ownership boundaries and data safety expectations.

---
description: Backend API rules
globs: ["api/**/*", "server/**/*", "src/**/*.{ts,js}"]
---
Keep validation close to request boundaries.
Do not widen auth or database permissions without explicit review.
Prefer existing service helpers before adding new clients.
Run targeted API tests for route, schema, or migration changes.

Generate A Custom Rule

Use the local generator when you want a project-specific .cursor/rules/project.mdc file with stack, commands, style, and review expectations filled in.

FAQ