This is a build session, not a lecture. Plan mode. Sub-agents. Watching Claude fetch repos, study your workspace, and sometimes make better decisions than what you asked for. The point isn't to follow along exactly. It's to see how a real build actually happens. What stood out?

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.

Ill be making a bigger write up here shortly on all this but lots of questions, answers and more questions. Play this in the car, on the way home from work or use it like another lesson!

$200 cash prize. One winner. Let's go!!!! THE CHALLENGE: "The Fake Client You just got hired. Here's your client 👇 - 📎 Download the full client brief attached to this post. YOUR DELIVERABLE: - A complete brand voice document for Ruff Cuts. - How you structure it, how detailed you go, what sections you include, how you get AI to nail the tone... that's all on you. - Same brief. Wildly different outputs. Show us what you've got. 💰 PRIZE: $200 CASH - One winner takes it all. 🗳️ HOW WE PICK THE WINNER - Community vote. Your fellow members decide. 📅 DATES - Submit by: Saturday, April 25th at 12:00 PM EST - Winner announced: Monday, April 27th at 12:00 PM EST 🎟️ WHO CAN ENTER - Premium and VIP members only. - Not a member yet? You know what to do. 📝 HOW TO SUBMIT - Drop your brand voice guide in the comments below. Text, screenshots, PDF, whatever works. Just make sure we can see it. ⚡ A NOTE ON FUTURE COMPETITIONS - This first one is straightforward on purpose. We wanted to start simple. - They won't all be like this. Challenges will get harder, more creative, and more technical as the weeks go on. Enjoy the easy win while it lasts. First competition. First winner. First $200. - Who's taking it? 👇

An ex Anthropic researcher just leaked 10 prompts to help you optimize your prompting. ## Prompt 1: Context Brief (The Map Claude Actually Needs) Never jump straight into a question. Start with rich context: ``` You are helping me with [specific goal]. My background: [your role + company/project + constraints]. I've already tried [X and Y]. I'm stuck on [Z]. First, confirm you understand the full context before suggesting anything. ``` Internal tests showed this single change boosts output quality by 41%. Claude isn't psychic — give it the full map. ## Prompt 2: Force Visible Reasoning (Chain-of-Thought on Steroids) Don't ask for answers. Demand the process: ``` Before giving any final recommendation: - show your full step-by-step reasoning - explicitly list every assumption - flag uncertainties and confidence levels (low/medium/high) - only then deliver the polished answer. ``` This pulls out Claude's hidden reasoning layers. You don't just get an answer — you get an auditable thought process you can actually trust. ## AND MORE - see attached files. From @kyronis_talks on X