How to Add a .cursorrules File to Steer Cursor

Cursor reads a rules file at the root of your project and feeds it to the model on every request. A few crisp lines about your stack and house style stop you from re-explaining the same things in chat all day. This guide adds one and confirms Cursor honors it.

What you need

• Cursor installed with a project open
• A clear idea of your build and test commands
• About 5 minutes

Step 1: Create the rules file

Place a .cursorrules file at the repo root. Keep it to short imperative bullets covering stack, style, and anything surprising about the layout.

- Stack: React + TypeScript (strict), Vite, Vitest.
- Use function components and hooks only; no class components.
- Imports: named exports, sorted, no default exports.
- Run the test suite mentally before suggesting an edit.
- Money is integer cents, never a float.

Step 2: Reload so Cursor picks it up

Cursor loads the file when the workspace opens. After creating or editing it, reload the window so the new rules take effect.

> Developer: Reload Window

Step 3: Test that it sticks

Ask for something that would expose a convention. If the rules loaded, Cursor uses named exports and cents without being told.

Result: Cursor starts every request already knowing your stack and style, so its suggestions land closer to mergeable on the first try.