Add Composer conversations to repo

Feature Requests
1

There’s an old adage: don’t commit generated files.

While that’s not a hard and fast rule these days, it made me realize, that my conversations with Cursor in composer are really important. The code generated from it is almost secondary. But I’m not committing the conversation to github, so it gets lost from my future, or for my collaborators.

Is there a standard way to capture all composer conversations in the repo, so that when I commit source code, i capture the history of how we wrote the code together?

1 Like
2

We had a similar rationale and ended up with following instructions in .cursorrules

Log user prompts to .meta/prompts.md file.
Log brief report of what you did, formatted as bullet points, to .meta/steps.md file.
If you've learned something new about the project from either the implementaion or the conversation, log it to .meta/knowledge.md file.
2 Likes