Debugging .cursor/rules

Is there a way i can debug how the .mdc files create are used?

For example, can I turn on some sort of profiling or developer tools settings that will show when/if a file is hit or influencing the model?

3 Likes

you can add to each rule file a statement at begin what it must output, like a keyword?

Add at the top this:

Start all responses with: “:memo:(rule) :”

I have yet to see any rule trigger at all, so I’d like something even more basic than that.

I do see them in the rules list via the ui

Nathan

many people asked the same questions here in the forum. they provided screenshots or mdc file text to review whats the issue.

Most likely your ‘description’ field does not tell the AI when to apply that rule properly.

Why do I need to guess? It should tell me that nothing was hit or that it’s trying to process but finding nothing. The assumption should be that the software covers over my incorrect config, not that I have to read the mind of the app.