Here’s a short presentation to cursor-rules-cli, a tool for bootstrapping Cursor rules
I also looked at /Generate Cursor Rules today and had to laugh quite a bit. Your approach is exactly the same and just as absurd.
Your rules, which is only a small part, mixed with a documentation, a developer workflow, a project planning and the architecture, generated from the codebase and the documentation, which in the end doesn’t have much to do with rules anymore.
Your sequence is completely incomprehensible to me!
I first create a planning, the architecture and a workflow, from which you can then create rules.
Or is this supposed to serve a different purpose that I just don’t understand?
I will add in the future the option to choose between code guideline templates. Right now, what I needed the most for my projects, was to make sure the Agent knows what that project is, it’s structure and what rules to follow. That’s what project-structure.mdc is for.
cursor-rules.mdc is for the agent to create other rules. e.g. Create a template rule for new screens that are following the format of <tag_file>
task-list.mdc is more for vibe-coders that want to create a PRD for the feature and have the agent follow that.
My CLI was inspired by Elie Steinbock’s video
I have seen the linked video.
90% codebase 10% rules in the mdc files.
There are no clear rules for me, rules should describe how the agent does something and not what.
I also understand your concern.
What you need is a documentation about the project with structure, architecture and so on, so that the agent knows what the project does.
Let the agent do that as a workflow.
What you really need is a memory bank that does two things for you at the same time: firstly, it keeps track of what your project is doing and secondly, it keeps track of the status of your project so that the agent can continue to develop it.
Take a look at GitHub - vanzan01/cursor-memory-bank: A modular, documentation-driven framework using Cursor custom modes (VAN, PLAN, CREATIVE, IMPLEMENT) to provide persistent memory and guide AI through a structured development workflow with visual process maps. or Cline Memory Bank | Cline
A rule should not describe what is being built,
but how the AI proceeds, decides, thinks or structures.