https://docs.cline.bot/improving-your-prompting-skills/custom-instructions-library/cline-memory-bank
From what I’ve seen, enthusiasts prefer Cline in almost every regard sans cost (which is a big one for sure) and the memory bank feature is near the top of the list as to why.
wow, this looks super interesting. thanks for sharing @zerk1
How do you get it to work with Cursor?
So many awesome ideas to take away from the cline docs. I started with an old version of this doc and evolved it into something much simpler and works as well with cursor + claude sonnet. Looking at this updated version is giving me some other ideas to work in to what i describe as my current workflow:
GitHub - bmadcode/bmad-news - the main branch is a starter project with the intent of trying this out. if you check GitHub - bmadcode/bmad-news at BMAD-ATTEMPT-1 - this is an example of using the workflow - look in the .ai folder to see the output of the memory files and PRD that the ai used to build out all of the listed stories (tasks) in the prd.
basically how this works is - there is a cursor rule that describes the workflow and every new composer window attaches to this rule and knows to check for a prd, check the story or task list, and only work 1 at a time. for each 1 it will create a draft story file, wait for approval or corrections, and then implement the story, marking progress and adding dev notes or commands to it as needed. once a story is done, I will start a brand new chat, and it will know to create the next file and work from it.
either way the main key is have a good .cursor/rules file that will follow the approach as you outline. mine has evolved to cursor-xml-rules-trial/.cursor/rules/prd-story-workflow.mdc at main · bmadcode/cursor-xml-rules-trial · GitHub version which is working out really well…
SpecStory provides that solution through export of chat etc. it can be automatically referenced by Cursor as its in your files.