User
Write something
High Tea is happening in 12 days
Pinned
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
6374 members have voted
Pinned
☕ June Tea Schedule
Sat, June 13 3pm: High Tea Sat, June 20 2pm: Afternoon Tea 3pm: High Tea Sat, June 27 2pm: Afternoon Tea 3pm: High Tea Mark your calendars and we'll see you there!
☕ June Tea Schedule
Pinned
🚨 You've been asking when the Lyceum opens. The waitlist is live. 🚨
The waitlist is up and seats are limited, so this is your nudge to go lock yours in. 👇 New here? Quick context. 👀 The Lyceum is Jake's live cohort program built on ICM, the methodology 35,000 people in this community are already using to get real results with AI. The short version: folders over agents. You learn the layer underneath the tools, the one that keeps working when the next model drops. Full breakdown is on the site. Here's what's inside: 🎯 Three cohorts, Technical, Business, and Creator. Same methodology, built around what you actually do. 🎥 Live sessions with Jake and a full team of instructors. ♾️ Lifetime recordings, written curriculum, and a private cohort Discord. 📜 An Eduba ICM certification you can put on your resume. And a guarantee no course makes: ✅ You leave with a working product, or the team finishes it with you. ⏳ Seats are limited and this community moves fast, so the math is not in your favor if you wait. 💡 Pricing and start dates aren't public yet. The waitlist sees them first, gives feedback on timing, and gets in before the program opens. Everything you want to know is on the page. If you already know this is for you, get on it. 🔥 👉 https://lyceum.eduba.io
Daily ICM Tip: If a stage needs a paragraph to explain what it does, it's actually two stages.
The trap everyone falls into when they're new to this is building a folder like '02_analyze_and_draft', and then wondering why the output is mushy. The agent read the research, formed an opinion, and committed to prose all in one pass, so you can't see where the thinking went sideways. There's no edit surface between "what it concluded" and "how it wrote it up." When the draft is wrong, you're re-running the whole thing instead of fixing the one bad handoff. "One stage, one job" isn't a tidiness rule, it's a debugging rule. The folder boundary is the review gate. Cramming two jobs into one stage doesn't save you a step. look at any CONTEXT.md and read its job out loud. If you naturally say "and" like, "it summarizes the sources and picks the angle" that "and" is a folder boundary you haven't cut yet. Every 'and' in a stage's job description is a review gate you're throwing away.
0
0
Daily ICM Tip: If a stage needs a paragraph to explain what it does, it's actually two stages.
Remember that YOU are still valuable when troubleshooting
Wanted to share something fun that Claude pointed out to me while troubleshooting a website issue today. Being able to troubleshoot without AI is becoming more of a common thing these days. Don't forget that it is a TOOL and not a REPLACEMENT.
0
0
Remember that YOU are still valuable when troubleshooting
1-30 of 1,512
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by