How to Set Project Rules in Cursor

Cursor can read a project rules file that it applies to every AI edit in the repo. Setting it up once means you stop repeating the same conventions in each prompt, and the editor's suggestions arrive already shaped to your house style.

What you need

• Cursor installed with a project open
• A short list of conventions you care about
• About 6 minutes

Step 1: Create the rules file

Project rules live in a rules folder at the repo root. Create the folder and a rules file inside it.

Step 2: Write crisp, imperative rules

Short commands work better than prose. List the conventions you most want enforced and keep each to one line.

# Conventions
- TypeScript strict; never use the any type.
- Named exports only, no default exports.
- Co-locate tests next to the file they cover.
- No comments that just restate the code.

Step 3: Confirm Cursor applies them

Ask the editor for a change that would normally tempt a default export. If the rules are loaded, it uses a named export without being told.

Result: Cursor applies your conventions to every edit automatically, so you stop re-explaining house style in each prompt.