Crazy how Jake’s method worked for my use case. I added n8n skills so it can work with 400+ nodes depending on my brief. I also added Supabase skills, trained it to learn new things, evaluate each node, and even act like GitHub for n8n. It literally saved me a month or more while building this n8n workflow bot with Supabase for multiple chat platforms like Telegram, Google Chat, and more. It also includes bot admin features where I can manage which reps have access to the other bot. The n8n workflows built with Claude can process files, let users chat naturally, answer questions about uploaded files, accept file uploads, and analyze multiple files at the same time. Compared to the vector store approach, this feels way more advanced because it can handle multiple data sources at once using an expert-level Supabase setup, with everything built through Claude. At first, I only built the command center to solve one problem: What if I have multiple clients? How can I switch which client projects i'll be working and access their credentials easily in one click without telling Claude which client project this belongs to? But I ended up taking it further. Now it lets me monitor everything, add new clients and client app credentials (e.g supabase, telegram, etc), and whitelist which workflows each client has in their n8n account—so those are the only ones the app can manage. Adding more feature once I have extra time but IT WORRRKS LIKE MAGIC! Got Super LAZZYYY creating this workflow from scratch but sometimes a simple idea turns into something much bigger once you start building.

Okay don't judge me on the title. It's actually what'll help you save up to 75% tokens while your using any Cloud LLM model. So as you can see in the screenshot below, there's this dev that made claude speak in "caveman" terms. Turns out that saves tons of credits for you. Tbh the more AI evolves, the more dumb and easier ways to save tokens arise, maybe soon enough the em dashes and 50 line answers would be eradicated by default? Anyways, here's the link to the post if you'd like to snoop around there: https://www.reddit.com/r/ClaudeAI/comments/1sble09/taught_claude_to_talk_like_a_caveman_to_use_75/

A friend of ours @Joseph Fioramonti built a tool called Constellations (If you have a watch or attended the first ever afternoon tea session. You'll know who I'm talking about). It measures something most people and most companies get wrong: the gap between what you think you respond to and what you actually respond to. Take it here 👇(also I am NOT getting paid for this and this is not some sponsored thing. Joe does really cool work) https://gen.constellations.app/constellations/survey/d269cab5-coca-cola/skool 📋 How it works: You'll see a grid of Coca-Cola images across two pages. Drag the green (+) dots to the images that make you want a Coke right now. Drag the red (-) dots to the ones that don't. Hit submit. That's it. 🧠 Why this matters: Every day we interact with systems that run on words. Search engines, AI tools, prompts, interfaces. The words we use are becoming instructions. They're becoming code. But here's the problem. If someone asks you "what kind of marketing works on you?" you'll give an answer. And that answer will be mostly wrong. Because desire and language live in different places. You feel a response to an image before you can explain it. You scroll past something or stop on something before your brain catches up with a reason. Constellations measures that gap. The space between what you say you want and what you actually respond to. This is the same problem companies spend millions trying to solve. It's the same problem you'll run into when you build anything that depends on understanding what people actually care about. And it's the kind of thinking that separates people who build things that work from people who build things that look right on paper. Take the survey. @Joseph Fioramonti will compile the results And provide a report shortly! He is an expert in branding and psychology and can come up with some really amazing reports.

I was sharing our community with our senior developer/director and telling him that what we’re doing here is going to change how we structure things in the company and create better results using Claude Code. I’m currently part of the lead team developing the company’s AI assistant model with multiple structured agents and layered analysis systems designed to support precise sales and marketing execution. I told him that I couldn’t really afford an enterprise-level account for Claude, so I haven’t been able to fully test everything I’ve been learning here as a VIP member. He spoke with the higher-ups and secured a 5-seat plan for me so I can continue applying what I’ve been learning, help the business grow in the future, and train the team using @Jake Van Clief notes...

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.