Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Elie
@elie
Since I open sourced my .mdc rules for Cursor I've been getting a lot of questions. Here are all the answers in one place: 1. Isn't 20 mdc files too much information for Cursor? No. This is what .mdc files solve. Cursor Rules file is now deprecated. You no longer provide all your information in one go, but in small chunks (.mdc files). Each of my .mdc files is <50 lines. 2. Do you need to manually tag Cursor? It can help. There are 4 options for rules: a. Always - the rule is part of every chat b. Auto attached - e.g. auto attach whenever you're chatting about ".tsx" files, or "tailwind.config" file. c. Agent requested - the agent can request to read the file. This is what I use most of the time. The agent decides whether to request a rule based on the description you set for the rule d. Manual - only applied when tagging it. I mostly use c. And I'll often manually tag the a rule as Cursor won't always read it otherwise. The Cursor team says they're improving this. https://getinboxzero.com/github
2 replies
6 recasts
42 reactions
Elie
@elie
3. How do I write the rules? I have a cursor-rules.mdc that writes rules. Easiest way to do this: * Share a snippet of code with Cursor (command-shift-L on relevant text) * Tag the .cursor-rules.mdc file * Ask Cursor to create a new .mdc file for this pattern Pro tip: Cursor is a little bit buggy here. I prefer to do this in "Ask" mode and copy the result into an mdc file. Sometimes you'll see Cursor show empty files when you do this in "Agent" mode.
1 reply
0 recast
6 reactions
lambda
@itzlambda.eth
I recently learned that cursor rule use is be divided into two steps: injection and activation. Just injection the rule using `applyAlways: true` is not enough for the rule to be used, this would just inject the rule into the context but it doesn't mean it will be used. See: https://forum.cursor.com/t/a-deep-dive-into-cursor-rules-0-45/60721
0 reply
0 recast
2 reactions
