Room for improvement? · Clief Notes

Room for improvement?

I've been building with Claude Chat (I call Claude) and Claude Code (I call CC) everyday. I've been providing trade knowledge and design decisions with Claude and just copying and pasting over to CC to build it, then I test in browser, take back any additions, critiques, alterations, etc. to Claude and we revise. Rinse and repeat.

I've thrown a few ideas at Claude to propose additional work that can be done while I'm not available that we could use CoWork (I call CW) to build. So far it's only been prototypes of what the future model would look like on a grander scale, but nothing has gotten that far yet.

My process with Claude and CC feels like it can drag on sometimes... I want to build this thing properly right from the start, so I've come to terms with the speed of it all, but I thought I'd check in with the masters and see if you can think of any holes or gaps I can fill.

We'll start with a diagnosis of whatever it is we're going to add or improve to see what kinds of other things might be affected by it's addition. Then we write a spec that goes into our CONTEXT bible. Then we do a build prompt that I hand to CC, who then builds it. Now we've also built a harness for the whole thing, so before each build we also add in a layer of building on to the harness, which comes with it's own checks, both surgical checks and full run sweeps. A full run is starting to take over an hour to get through now, so needless to say some of the progress that I made early on before it got this big felt a lot better than the speed that the whole project is moving at now. After both harness and build have happened I'll do a screen test depending on what was changed. We'll commit after a full green pass, and then move on to the next step up the mountain of steps that this has shaped out to be.

Without having to go into too much detail about what the project is about (I've been working full time and just trying to grind this out on evenings for a few hours a night and weekends where I spend usually >12h trying to get through this thing) what do you guys think might make this process run a little more smoothly?

The folders I use are a CLAUDE.md, CONTEXT.md, VISION.md, HANDOFF.md, PHONE-HANDOFF.md (for when I'm trying to do what I can at work on breaks. I can't build since everything happens on my PC at home, but I try to get through some trade questions or designs through my phone app Claude Chat ((I call CP 🤣)) so that we can have build sessions roadblocked less by the time I get back to my computer), README.md, REFERENCES.md, SESSION-NOTES.md.

So far everything I've been doing is being done in a Test Folder - CLAUDE.md - Project Folder - everything else.

Tips and tricks on what you guys have been seeing work well?

*Disclaimer - my depth of knowledge on these things is still quite shallow. I'm learning as I go. Been doing it since I joined this group back in whenever that was.

Something else I wanted to ask about was the Second Brain analogy. Pros? Cons? Coles Notes?

Keep up the awesome work people! 👍👏🙌

7 comments

Room for improvement?