I saw the version 0.45,how ".cursor/rules" work

any desc ?
how does it work ? any information ?

1 Like

Hey, this is being discussed in this thread.

Can we have multiple .cursor folders in a monorepo, or just one at the project root?

I’ve read that we should create a .cursor folder, but I’m unclear on whether only one folder is allowed at the project root or if we can have multiple—for example, one in the frontend folder and another in the backend folder in a monorepo setup.

If only a single .cursor folder is allowed, how should we structure the .mdc files to handle both the frontend and backend? Could someone share an example or clarify the best approach for organizing this in a monorepo?

Hey, you don’t need to create anything manually. You can go to the Cursor settings and create rules from there. You can create as many rules as you want, but they will all be located in the .cursor folder. Then, depending on the task you’re working on, you add the necessary rules to the context.

1 Like

i had been try a project contain frontend and backend in one folder. cursor always gets the root directory of each project wrong.

I think the front-end and back-end projects should be separated.

Every time it executes the wrong script root directory, it will repeat the trial and error process, wasting a lot of time and tokens.

1 Like

Thank you for the clarification Dean! :pray:

I just found this hint in the editor, when creating a rule through the Cursor Settings:

Screenshot 2025-01-26 at 15.05.15

So basically the description text is really important for Cursor to decide which rule file to use. Also you can specify the folder and file extensions (globs) per rule.

I didn’t test it yet, but will report how it goes.

yeah, and u can use @rules to reuse highly reusable prompt words

1 Like