# Epic Cursor Rules Generator Improved! **URL:** \ **Category:** Built for Cursor\ **Created:** [February 12, 2025, 6:06am UTC](https://forum.cursor.com/t/epic-cursor-rules-generator-improved/50194 "2025-02-12T06:06:28Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bmadcode](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bmadcode/32/23874_2.png) [@bmadcode](https://forum.cursor.com/u/bmadcode)\ **Post date:** [February 12, 2025, 6:06am UTC](https://forum.cursor.com/t/epic-cursor-rules-generator-improved/50194/1 "2025-02-12T06:06:28Z")
Got an idea from an article but it was not fully optimized to work well with cursor mdc files regarding rule selections, formatting with xml, and populating the front matter. Here is a repo with a good example and readme of how to make use of this system to build up and generate useful granular rules automatically so your ai agent learns and improves over time! > **[GitHub - bmadcode/cursor-xml-rules-trial](https://github.com/bmadcode/cursor-xml-rules-trial)** > > Contribute to bmadcode/cursor-xml-rules-trial development by creating an account on GitHub. since I have started testing with this, it does seem that xml produces some optimizations and I am finding with really well crafted description front matter, it gets picked up well when needed almost every time. once the main cursor-rules.mdc file is in place, you can basically ask the ai to create any rule you can imagine, and it will structure it with maximal bias towards xml, front matter selection and ai usage optimization. ---
**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\ **Post date:** [February 12, 2025, 7:21am UTC](https://forum.cursor.com/t/epic-cursor-rules-generator-improved/50194/2 "2025-02-12T07:21:20Z")
Are you by any chance using Claude only? As Claude is optimized for XML system prompts. Other LLMs may have sometimes limitation. But overall XML nicely shows where there is a begin of some rule part and where there is an end. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [February 12, 2025, 10:42am UTC](https://forum.cursor.com/t/epic-cursor-rules-generator-improved/50194/3 "2025-02-12T10:42:52Z")
Hey, thanks for sharing this. It could be helpful. ---
**Author:** ![bmadcode](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bmadcode/32/23874_2.png) [@bmadcode](https://forum.cursor.com/u/bmadcode)\ **Post date:** [February 18, 2025, 5:05am UTC](https://forum.cursor.com/t/epic-cursor-rules-generator-improved/50194/4 "2025-02-18T05:05:39Z")
I have done more research and found that the XML rules really dont help that much - and it is better to use a combination of yaml front matter, markdown, and xml tags. also rules function much better with examples I have found. I have a new rule generator template and script also shared in this other thread. > [@Ultimate Rule Generator - No more failure to generate and Private Rules!](https://forum.cursor.com/t/ultimate-rule-generator-no-more-failure-to-generate-and-private-rules/51782): > > There have been a few attempts and shared rules that would generate other rules, but they all seems to have a few problems. After quite a bit of research, tweaking, and figuring out what the optimal format of rules might be (research in the readme linked below), I have created a template with a rule that will: Always save or update a rule (does not fail to write or create a file occasionally Optimize for auto rule selection through optimized front matter descriptions Usage of mermaid diagram… ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [June 18, 2026, 10:28am UTC](https://forum.cursor.com/t/epic-cursor-rules-generator-improved/50194/5 "2026-06-18T10:28:26Z")