Cursor setup: .mdc rules, agents.md, and hooks — what actually works? #2
Unanswered
oliviacraft
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A common question in the Cursor community: how do you structure
.mdcfiles,agents.md, and hooks when you have multiple languages in the same repo?Here's what works:
For multi-language repos (Python + Java + TypeScript):
Three separate
.mdcfiles in.cursor/rules/:Set to Auto Attached — only loads when matched files are in context. Token-efficient and precise.
agents.md vs .mdc:
agents.mdin a subdirectory acts like a scoped Always Apply rule for that folder. Works, but a named.mdcwith explicit globs is more maintainable.Hooks vs skills: Hooks fire automatically on tool events (after Edit, after Bash). Skills are invoked on demand. Use hooks for always-on side effects, skills for optional workflows.
Full setup guide as a Gist: https://gist.github.com/oliviacraft/281f8ba971d238e8ff0ae87e2e99f21c
Free starter kit with pre-built rules for 14 stacks: https://oliviacraftlat.gumroad.com/l/pomoo
Full pack ($27): https://oliviacraftlat.gumroad.com/l/wyaeil
What's your setup?
All reactions