When working in a team it would be nice if cursor could have a .cursor-learnings-file it would add it’s learnings to. So when given feedback it will suggest adding a learning to that file. Such that project specific gotchas are documented. The learnings file is not gitignored, so it is part of the pull request and can potentially be used to generate documentation. In order to avoid unnecessary merge conflicts .cursor-learnings merge=union is suggested added to .gitattributes
Thanks for the suggestion!
We do see Cursor’s “memory” as the next area to work on, so we appreciate the idea. Keep an eye on our future updates for some features in this area.