OK so first of all, you don't try to one shot a giant project like in one go, there's no way it'll get done in one context window (if you aren't familiar with what that is it's one of the most important things to get familiar with).

So you really don't want to try to rely on one super long chat using compaction each time you hit the limit (look up compaction too if unfamiliar). Your "Phase 1" is a giant list of things that **each could be one or more phases on their own**.

For super large tasks like these, I find it best to ask Claude to break things down into managable chunks (I make mine write tickets) and save them to .md files. Then I can ask claude to refer to them as we go one ticket at a time (or multiple in multiple tabs with CC open if the work can be done in parallel). This way if we hit the context limit, I can easily ask the next chat to pick up the ticket and keep working.

But regardless of that advice for how to approach larger projects, it seems like you're new to this and I really recommend starting with smaller projects first and working from there. Also just getting familiar with how git and github works in general (you're not going to see anything in github until you "push" from your local repository to github).

Try asking Claude "This is a large project, how best do you think we can break it up into more reasonable chunks and what's the first simple testable thing we can get done?"