I’m working on setting up some cursor rules for my projects and could use a bit of advice on how to make them as effective and efficient as possible. I’ve already picked up some great tips from this blog post on mastering cursor rules Best Cursor Rules for Cursor IDE, and they’ve been super helpful!
But I’m a bit stuck on one thing: when explaining the project for the rules, should I go for a more generic intro like, “It’s a NextJS platform using TailwindCSS,” or get more specific, like, “It’s a NextJS platform that helps users schedule posts for Twitter and other social media”?
Would love to hear what approach works best for others!
Also, if you’ve got any extra tips for writing solid cursor rules, feel free to share—I’m all ears!
I ask cursor to create context.md on /src and I ask him to update it every time because sometimes it rushes to code modification without telling too much why. It works for me like this
My question is whether the cursor rules should focus only on the code and have a separate context.md file to explain the project, like you do, or if we should include project-related information directly in the .cursorrules file.
Going to Cursor Rule Maker and giving it that same prompt will probably get you better results as its trained on high-quality .cursorrules examples from the community. It will include typical best practices and things like that
The main difference is you would need to manually include the context.md file into your chats. The .cursorrules file is automatically included in context without needing to @ it in every chat