Pinned
👑
⭐
19d •
Welcome to Clief Notes. Here's where to start.
1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. 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 join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?
Pinned
👑
⭐
57m •
New Clief Notes Logo!
My Cousin @Ryan H. was tasked with making me a new logo for the group (the old fashioned way, not much AI help here) and I think he SMASHED it out of the park. Perfect nuance, what do you all think?
Pinned
4d •
🏆 WEEKLY COMP #9: THE EDITOR 🏆
🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 💻 Code review editor for a specific language and level (junior TypeScript, senior Python) - 📊 Pitch deck editor for pre-seed founders - 🎨 Grant application editor for arts nonprofits - 📄 Resume editor for career switchers into tech - 📰 Op-ed editor for policy publications - 🎙️ Podcast script editor for interview shows - ⚖️ Legal brief editor for civil litigation - 📋 Product spec editor for early-stage PMs - 🎓 Academic paper editor for one specific field The more specific, the better. "Writing editor" is too broad. "Op-ed editor for tech policy publications targeting a policy audience" is right. 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your editor is a folder with five things: - 📄 identity.md (who the editor is, what work they review) - 📐 rules.md (how they critique) - 💬 examples.md (what good critique looks like) - 📚 reference/ (style guides, checklists, frameworks the editor uses) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the editor. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK An editor is NOT a rewriter. An editor doesn't do the work for you. An editor surfaces what's weak and pushes you to fix it. That distinction is the whole assignment this week. When someone hands the editor a draft, the editor shouldn't produce a "fixed" version. The editor should point at the three lines that don't work, explain why, and hand it back to the writer to solve. ✍️ Generic feedback like "consider strengthening your intro" is a fail. Specific feedback like "your intro assumes the reader already knows what a Series A is, but this pub is read by generalists, so lead with the stakes instead of the jargon" is what a real editor does.
👑
⭐
2d •
🛠️ New tool: ICM Architect
I explain the details about it on today's high tea . I built a Claude skill that turns a process, an idea, or a messy folder into an ICM workspace. The folder structure does the orchestration. Numbered folders carry the order, the hierarchy scopes context, and plain markdown files hold state. One agent walks the right files at the right time and does the work a multi-agent setup would. Repo: github.com/RinDig/icm-architect 📦 What it does Two modes. 🔨 Build. You describe your work and it pulls out the structure already sitting in how you talk about it. The stages, the points where you stop and check, what stays the same every run versus what is new. Then it picks one of five proven forms and scaffolds the smallest workspace that carries the job. ♻️ Restructure. Point it at a folder, repo, or vault you already have. It reads every file, sorts each one by role, shows you a migration map, waits for your yes, then moves and checks the result. 🧩 The five forms Pipeline, umbrella, record library, knowledge bundle, context map. They mix and nest, so most real workspaces use more than one. ✅ The walk test Every result gets checked cold. An agent with no memory has to open the root, find its way, act, and report status from the files alone. If it can't, the structure gets fixed until it can. ⚙️ How to use it You can honestly just tell claude to download it from the link, but if you're using codex or something else it will just have to restructure the claude.md to agents.md Or if you want to do more Hands-On install Claude Code: drop the folder in ~/.claude/skills/icm-architect/, then say "ICM this" or "build me a workspace for X." Claude apps: zip the folder and upload it under Settings, then Capabilities. Fork it, break it, tell me what you built. 👇
3d •
What books are you reading (or listening to) these days?
I've been reading more lately because i'd like to think of myself as a lifelong learner... but also partially because I had a bunch of credits piling up in Amazon's audiobooks app (so technically I'm not reading, I'm listening). Recently it's been Range by David Epstein and Greenlights by Matthew McConaughey. Greenlights was partly just fun, partly curiosity about how a celebrity writes a book. McConaughey reads it himself, and honestly, it's cool to hear where he puts his own emphasis on certain words + sentences because he's the one who wrote them. One chapter in Range stuck with me though. There's a section about "centaur chess"... after Kasparov lost to Deep Blue (IBM's chess supercomputer), they started running tournaments where humans play with computer assistance. The surprising result: the winners weren't the best grandmasters, and they weren't the strongest computers. They were average players with the best process for working with the machine. A mediocre player who knew how to use the computer well beat both grandmasters and supercomputers playing alone. That feels like exactly where we are with AI right now. The game isn't "how good are you at marketing" or whatever your domain is anymore. It's "how good are you at working with this superhuman teammate." And how good are you at understanding, building, + utilizing the new, A.I teammate. Anyways, two things I'm curious of: 1. Any Systems Thinking book you'd recommend. (Since systems thinking is essentially the core/foundation of everything we do here.) 2. Any book outside your usual lane that helped you in ways you weren't expecting. Something you picked up deliberately or not, and it ended up shifting how you think. Curious what everyone is reading these days. Cheers! Shawn
1-30 of 2,626
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
+1565
2
+1102
3
+973
4
+698
5
+640
Powered by