Naming .cursorrules and having multiple files?

Discussion
1

I should start by saying I don’t really know what I am doing :slight_smile:

I have set up 3 .cursorrules files and named them each something:
-rules.cursorrules
-implement.cursorrules
-structure.cursorrules

I use the rules for the normal rules usage that the AI should follow. I use the implement file to keep a running to do list with implementation plans. I set this one up because I was having the AI generate a plan for me but it got so buried in the chat window that it forgot it or the chat window started running so slowly that I had to start a new window. Essentially just a file to reference what the current plan is so that I can @ reference a notepad indicating to work on the implementation plan. This aspect has been working pretty well.

I use the structure file to try to enforce the file system structure as I have alot of issues where the AI wants to create a new file to implement something when that file already actually exists. This has not been working that great. The AI doesnt seem to be able to see the actual file structure even if I share codebase or add all the relevant files as context.

In short, I was trying to create a system of checks and balances.

I guess my questions are: am I causing any potential conflicts or confusion by having multiple .cursorrule files? I also dont see anyone else naming them, just wondering if there is a reason why? Is that causing potential issues?

2

I’ve not seen anyone use that naming pattern should that work? It makes sense that it should… I alawys thought the file must be .cursorrules I believe Cursor is designed to only read that file automatically (when it works as desinged, that is.)

I suppose you could get into the pattern of manually including the relevant rule in your conversations, but I’m pretty sure it won’t read them by default unless it’s simply “.cursorrules” ? I could be wrong…

3

I changed the actual rules file I was using to just the .cursorrules to see if that changes anything. I have notepads set up to use as prompts that automatically includes references to the applicable rules files so that I don’t have to add them individually each time. For example:

Implementation Review and Update Process

  1. Review Codebase
    Compare the updated codebase with the plans outlined in the @implement.cursorrules file.

  2. Update @implement.cursorrules

    • Following the rules outlined in the @implement.cursorrules file, update each of the tickets in the “Open Tickets” section to reflect the current implementation progress. This should include updating the progress of each ticket’s requirements and implementation steps.
    • Move any closed tickets to the “Closed Tickets” section.

  3. Compliance Check

    • Ensure that the code is following the rules outlined in the @.cursorrules file. Do not comment on this in your response unless there is a non-compliance issue that needs to be resolved in the recent implementations. If there is a compliance issue, please provide a comprehensive, step by step plan to correct the issue and bring it into compliance.
    • If any new files or folders were added to the project directory in the recent implementations, the @structure.cursorrules file should be updated to reflect the current state of the file system. Do not comment on this unless there is a compliance issue that needs to be updated in the @structure.cursorrules file. If there is a compliance issue that needs to be updated in the @structure.cursorrules file, you should provide me with an updated version of the file.