Hi Cursor. I’ve been building custom tooling for a corporate registry of rules. I’ve even built a linter and “compiler” for rules, and a document generator for the rules, you can see an example here cursor-config/CURSOR-RULES.md at main · zackiles/cursor-config · GitHub. It’s been a real hit, and we have many lint-rules for Cursor rules now cursor-config/src/lint-rules at main · zackiles/cursor-config · GitHub. I’ll likely rename this project ‘cursor-workbench’ - you’re all free to steal this idea and incorporate it into cursor (I’d also be happy to help contribute to it - I might be the only super-nerd of Cursor out there).
I want to invest more time in this project, but I have an annoying stumbling block, your custom mdc editor strips out frontmatter fields that aren’t part of your spec, which strips custom fields my system uses to tag and organize rules for teams. Could you please not strip these when a file is saved?
Side note: if you’re looking to improve rules even further, checkout what this says. Part of what’s been implemented is a “compiler” for rules where I wrap them in a high-level system prompt (not shown in that codebase). I sort of reversed engineered Cursors use of priompt and the cursor agent and using a plugin I inject the wrapper directly into your system prompt. I wish I didn’t have to, but was the only way I could reliable get the ‘bare metal’ feel of controlling the system prompt and allowing things like injection of custom tools (teams package small scripts up with their rules in the registry). So my ask would be to give us a bit more exposure to the raw system prompt when you have a chance
Big fan, thanks!