Writing Cursor rules with a Cursor rule

158 点作者 adithyan_win大约 1 个月前

12 条评论

behnamoh大约 1 个月前

How long until such "rules" also become standardized (like we saw with MCP)? It feels redundant to have rules.cursorrules and rules.aiderrules where the rules content is the same. I predict companies will not only publish coding guidelines for their programmers, they'll publish these tiny coding rules for LLMs used in the company as well, so all code follows the same standards/idioms.

christophilus大约 1 个月前

I have found Cursor to be frustrating and exhausting to work with, even with my rules file. When it works, it’s like magic. But most of the time, it feels like working with a Jr. dev who has a bit of a concussion. Code review is wearying work, and using Cursor means you’re doing a lot of code review. I have never once gotten into a flow state with it.That was a long preamble to this question: any senior devs out there (20+ years) who enjoy using Cursor? What’s the trick?

评论 #43681580 未加载

评论 #43679393 未加载

评论 #43677226 未加载

评论 #43677866 未加载

评论 #43679155 未加载

评论 #43678245 未加载

评论 #43677481 未加载

评论 #43733487 未加载

评论 #43678532 未加载

vemv大约 1 个月前

Cursor in particular but also others are extremely flaky when it comes to applying rules.So the next generation of "rules" for Cursor, Claude Code, etc should have some predictability baked in, i.e. not be entirely driven by AI.Having rules driven by a vanilla, non-AI program ensures that they're actually, consistently applied, with some logs showing if/how they were applied.Of course, one can augment vanilla rules with some AI capabilities, but the main orchestration should resemble determinism.I suspect that the main reason why this isn't a reality yet is because costs could easily skyrocket. Personally I'd be willing to pay the extra buck if that means that my comprehensive rule system is actually doing something.

评论 #43678381 未加载

aledalgrande大约 1 个月前

Seems like we're rediscovering/reinventing the same thing over and over, this is very close to Memory Bank from Cline <a href="https://docs.cline.bot/improving-your-prompting-skills/cline-memory-bank" rel="nofollow">https://docs.cline.bot/improving-your-prompting-skills/cline...</a>I have seen a number of articles and Youtube videos posting more or less the same thing.

amiantos大约 1 个月前

This feels like a bandaid on a gaping wound to me. Maybe you're making certain aspects of using Cursor/Copilot Agent Mode less annoying, but they're still there and still annoying.In the parts of the open source LLM community that are interested in roleplay chat, the veterans seem to have the viewpoint that spending a lot of time tinkering to try to overcome the inherent flaws in this technology is relatively pointless; at a certain point, it's random, and the technology just isn't that great, you're expecting too much. Just wait for the next great model. But don't waste your time putting bandaids all over the huge flaws in the technology, you're still not going to get the results you want consistently.I can't help but think of that here. I don't want to spend my time managing a junior engineer with amnesia, writing Rules files for it to follow, come on now. We're supposed to pay $20/mo with usage limits for that? The promise of "vibe coding" according to all the breathless media coverage and hype is that it'll supercharge me 100x. No one said anything about "Cursor rules files"!I'll stick with Copilot's "fancy auto-complete", that does speed me up quite a bit. My forays into Agent mode and Cursor left me feeling pretty annoyed, and, like I said, I don't want a junior developer I'm managing through a chat sidebar, I'll just do the programming myself. Get back to me when Cursor is at senior or principal engineer level.

评论 #43678987 未加载

评论 #43680970 未加载

评论 #43678899 未加载

评论 #43680335 未加载

评论 #43682731 未加载

jredwards大约 1 个月前

I've found this a tractable approach, but sometimes not enough. My escalation pattern with cursor looks like this:1. Document everything that you're doing and update a core architecture or technical doc that the LLM can read.2. Update your .cursorrules with specific instructions for .cursor which can grow more specific as you nail down parts of your stack and the patterns you're following. This can be updated (by cursor itself) if you find the same problems recurring.3. I have pre-commit script which runs some internal scripts. If I find the IDE is STILL making the same mistake after I've documented it and added cursor rules, the nuclear option is to add a script here which verifies the integrity of whatever construct is being violated (e.g. tests go into this folder structure, env variables are consistent between these files, import of this model that the LLMs like is forbidden)I would add: any time you expect to be working on a particular feature / enhancement / refactor, have the LLM create a temporary document with a description and an implementation plan and work from that.In addition: I have a specific workflow for resolving testing errors or pre-commit errors which follows the above pattern: Document each failure and work through them one at a time, running the test script and updating the document between runs.I've established these patterns slowly with usage, but it has improved my experience a lot.

brylie大约 1 个月前

Hopefully, we'll converge on a standard, product-agnostic file naming convention, similar to .editorconfig. Are there any existing/emerging generic conventions, like .llm-instructions, that products like Cursor and GitHub Copilot support? This could be useful for teams and orgs with diverse LLM usage.

ccppurcell大约 1 个月前

Question for users of such tools: can't you ask the LLM at the end of the session to choose the most important parts of the context, compress it using your favourite tool, then decompress at the beginning of the next session?

评论 #43682039 未加载

DeathArrow大约 1 个月前

If someone needs a C#/.NET meta-rule, I shared one here: <a href="https://pastebin.com/EmNsTRwY" rel="nofollow">https://pastebin.com/EmNsTRwY</a>After quickly testing it seems to be reasonably good.

throwup238大约 1 个月前

Does anyone have a variant on this meta rule file that isn't React specific?

评论 #43678139 未加载

tyleo大约 1 个月前

I’ve been using more and more AI tools in my development and getting a lot of mileage. Cursor is the latest one I’ve adopted and it’s impressive even without rules.I’ll give this a try soon. Thanks for sharing!

jascha_eng大约 1 个月前

LLMs have shit memory and abstraction capabilities and just adding md files and more context is like trying to make a alzheimer patient learn to play the piano. Yes it kinda works to some degree to always repeat everything, but it's not true learning and just a bandaid.