@Alexander Paschka Really nice insight here Alexander. How did you get this client? What started this process? Eager to learn more on how you got into this position.

@Alexander Paschka Class response Alexander, thank you for sharing this😁 - when it came to your learning experience through this Skool environment, how did you go about learning things? In regards to the challenges you forsee, are you responsible for offering a solution to those for that client specifically or?

@Josh Bowen Hey Josh! Insightful stuff here. I've also recently looked at setting up Whisper locally on my GPU but couldn't get the hang of it. What do you do then if you need to ask Claude questions about your workspace and avoid passing that question into Claude Code? (to minimise token usage).. I find myself wanting to ask questions about my workspace, but I don't know how to do that via Claude when claude.ai isn't pointing to my workspace but claude code is? Hopefully the above makes sense ahah

@Josh Bowen THIS!

I'm personally using VS Code. As Jake has mentioned in his lessons. Spending too much time focusing on what IDE you use vs the actual layout/folder structure is not as important. VS Code is good enough for Jake, so it should be good enough for everyone here 😉

@Shirsho Guha Was just about to reply to suggest the same thing ahah. Good to see you cover that Shirsho! Nice one :)

@Jonathan Jarl Wellershaus Sup Jonathan- Yes there is a reason why you would have CLAUDE.MD and CONTEXT.MD separate. Claude.md = Top level identity and navigation. This file loads on every task and acts as the "floorplan" that the agent will always reference. Identity, folder structure, and routing tables will exist here. Context.md = The context files that lives inside each workspace folder. This tells Claude what the workspace is, what to do with it, and what to load & skip. Things like purpose, skills & tools, naming conventions are laid out here. There's a lesson in the classroom that goes over this in more detail which I recommend getting through to understand the nuance between both and how/why they exist separately.