I’ve been working to build out processes with the folder structure method. The only downside I see is if people aren’t literate with using Claude and setting up projects or vs code etc. You can build custom front ends to interface with to make life easier but this typically requires api calls to invoke Claude this way. Is there a way to build apps or guis that call on Claude in a folder structure process to run without using APIs so subscriptions can be used?

Claude design is fully released. It burns up tokens but it works very well, and allows you to automate the folder design process that I've been showing you all. My video will go on to how not to use it as I think there's still some limits to what it can be done, but it's the step in the right direction. Again, I've been telling you about building systems that will be amplified by updates, not replaced. This is a perfect example. I'm going to go ahead and make a nice long form video out about this. What do you want out of the YouTube video? Comment below what use cases you want me to explore in the long-form (and eventually course addition of course !) For those of you that have been studying this the past few months, how does it feel to be ahead for once!?

I’ve been following here for a bit. I’d like to say I understand the benefit and I understand the workflow. I have done a number of mini projects successfully and fully see the benefit and future of the technology. Where I am struggling is everything I use AI for seems to be one off tasks. Incredibly helpful but not repeatable. I struggle to find opportunity for workflows in my day to day work. I’m not smug enough to think that my work is that different from others and not able to be benefitted by the technology but I genuinely struggle to find use cases that last. How do you identify these processes in your life? How do you tell the difference between something that can be fully automated and something that benefits from an AI workflow?

For those who missed the first post or just joined: The Lyceum is a 12-week program we're building. Live instruction from Jake and the Eduba team. Small cohorts. Real projects. You build something from week one, not watch tutorials. At the end, a competition with real prizes. Eduba's first certification, backed by the same methodology we've used to train Fortune 500 teams. Now here's what we've locked in since then. The Structure Three 4-week sprints with a 1-week break between each. Not 12 straight weeks of grind. You build, you breathe, you come back sharper. - Sprint 1: Foundation — Core methodology. Everyone starts here. - Sprint 2: Application — You're building. Real project, real progress. - Sprint 3: Capstone — Finish what you started. Demo day prep. The breaks aren't fluff. They're built in so you can catch up, refine, or just live your life without falling behind. The Cohorts Same curriculum across all three. The difference is where your hours go. Technical — Developers, engineers, technical founders. You're building a tool or production system. 30% of your time goes to Claude Code and integrations. Another 30% to production systems and capstone. This is the builder track. Business — Ops, managers, founders, consultants. You're automating a process or designing a system spec. Heavy emphasis on workflow design (30%) and decision frameworks (25%). You direct the work without writing the code. Creator — Marketers, educators, solo operators. You're building a content production system. One person replaces the team. 25% on content pipelines, 20% on workflow design. This is how you scale yourself. Pick the track that matches how you work. The methodology transfers no matter which one you choose. A 4th Cohort? We're considering adding a team cohort if there's enough interest. This would be for companies that want to enroll multiple employees, or for people in the community who want to form their own team and build together. If that sounds like you, let us know in the comments.

This is the one that pays for itself. Point Claude at any page, pull structured data out. Product info, contacts, job listings, reviews, prices. Whatever's on the page becomes usable data. Try it on books.toscrape.com first. Then try it on something real. What did you pull?