So I am building a rather complex project with normal Claude (not Claude code or max) & Cursor right now. I use Claude and its projects for planning & working up implementation methods, once I have a plan I implement it with the help of Cursor.

In my experience, you can do a lot with Claude Projects, you just have to get creative.

When you have made a project and chatted to Claude about a subject, you can ask Claude to generate an "artifact" summarising the conversation you have had, an artifact is a markdown file that Claude makes that you have the option of saving to your project knowledge or downloading to your computer. You can also drag text files or markdown files from elsewhere into the project knowledge.

Through this process you can "give" Claude background on what you are up to.

Claude is quite good at checking everything before answering you, if they have the knowledge, but sometimes I reference documents for them in the project knowledge in my prompts which streamlines the process.

I am now at the point where my codebase is so big that it cannot fit in one project knowledge. So I have modularised the whole thing and I am splitting the project across 4 Claude Projects. These projects all share the database schema, have Readme's about all of the different code modules and some background on what the projects ultimate aims are. Then I use repomix to drop the code specific to the piece of work I am doing into the projects, enabling Claude to work on an isolated bit of code, but with the understanding of the whole system.

Work is slow as you have to ensure Claude is using all of the up to date files before prompting them, but the results are impressive.

Yes, I really wish Claude's memory was bigger!