User
Write something
High Tea is happening in 4 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
4516 members have voted
Pinned
🏆 WEEKLY COMP #3: THE SPECIALIST 🏆
💰 $325 CASH PRIZE 💰 That's a full year of Premium. Win this and your membership pays for itself. 📋 THE CHALLENGE You just got hired again. Different client this time. Meet Sarah, a freelance copywriter who's drowning in context-switching. 📎 Download the full client brief attached to this post. Short version: She works with three types of clients (SaaS founders, ecommerce brands, local service businesses) and starts from scratch every project. She doesn't need another tool. She needs a system. Your job is to build her a folder-based AI specialist she can drop into any Claude project. The folder IS the deliverable. 🗂️ THIS WEEK YOU LEARN ICM Up until now, comps have been "build a thing." This week you utilize the methodology taught throughout the community. 🧠 Folders as architecture. That's it. That's the whole concept this week. Your specialist is a folder with five things: - 📄 identity.md (who they are) - 📐 rules.md (how they respond) - 💬 examples.md (what good looks like) - 📚 reference/ (source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the specialist. Reusable. Shareable. Portable. 🎯 PICK YOUR SPECIALIST Don't pick copywriting. That's Sarah's example. Pick something YOU would actually use. A few sparks to get you thinking: - A salary negotiation coach - A meal planner that knows your dietary restrictions - A code reviewer for your stack - A real estate market analyst for your city - A technical recruiter screener - A grant writer for nonprofits in your space The more specific, the better. "Marketing expert" is not a specialist. "B2B email expert for enterprise SaaS targeting CFOs" is. 💼 WHY THIS ONE LANDS ON YOUR RESUME Real talk. Winning a comp in a Skool community doesn't get you a job by itself. But shipping a working folder-based AI specialist with a clean README and a public repo? That's a portfolio piece.
Pinned
Who's here? Drop your intro.
Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.
See behind the veil - full architecture
This took a few weeks. Not building. Training. Tweaking. Breaking. Locking. Running the same flows over and over until the architecture stopped bending. Everyone here knows ICM. What this is… is what happens when you actually live inside it long enough. Not theory. Not clean diagrams. Real load. A few things only showed up under pressure: - The moment where orchestrator wants to execute… and you don’t let it - The cost of letting workers “figure things out” vs forcing briefs to be exact - How fast token bloat creeps in when you don’t treat load surface as a constraint - The difference between a rule you wrote… and a rule you had to write three times At some point, things flipped. The system stopped feeling like something I was managing… and started feeling like something that was holding shape on its own. That’s when the real work began. What’s in here is not “a good setup”. It’s what survived: - multiple passes of weekly audits - repeated cold starts - real production friction - and a lot of “this felt right but didn’t hold” A few things I’d pay attention to if you explore it: - Where boundaries are enforced (not suggested) - What got locked into rules vs left flexible - How briefs are treated as contracts, not prompts - How little the orchestrator actually does Also interesting: The extraction itself. That process alone shows you what was structural… and what was just personal preference. → https://github.com/NFTYoginis/creator-orchestrator-template If you’re deep into ICM already, you’ll see where this goes. Curious what breaks for you — or what holds better than expected.
🏁 Foundations 2.4 Check-In
You just learned the book, movie, video game framework. Vote below, then tell us in the comments: name one thing in your work that you now realize is on the wrong layer.
Poll
428 members have voted
1-30 of 982
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by