Pinned
👑
⭐
14d •
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
👑
⭐
2h •
🏆 COMP #8 RESULTS: THE WILDCARD 🏆
📦 AND SOMETHING NEW: EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 WHAT WE DID DIFFERENTLY THIS TIME Every submission was cloned at the exact commit that was public when we read it, and read file by file. The brief. The identity. The rules. The reference layer. The code. Where a repo made a claim we could check, we checked it. Arithmetic recomputed by hand. Sample photos opened and compared against the outputs that cited them. Files diffed. Self-tests traced. Thirty-two repos, read at the code/word level. And one lens over everything, because it's the lens this whole community is built on: does the build keep the human's judgment where it pays and put the deterministic work in code, where it can't hallucinate? 📦 THE FEEDBACK PACKAGE This is the new thing, and it's for everyone not just the podium. 📦 COMP #8: THE WILDCARD - The Vault Every entrant gets a markdown file. Three parts: 1️⃣ The read. What your build actually is, and the strongest thing in it cited to your own files. Rule numbers. Function names. Your own examples. 2️⃣ One push. The single change that most improves your build. Not a list. One. 3️⃣ An idea worth naming something original in YOUR build, credited to you, that the rest of the community is told to take from. Plus links to the builds your feedback points at. Nobody walks out of this comp empty-handed. Thirty-two builds, thirty-two named ideas. The roster alone is worth the download. 📍 The package + the full write-up (what held up, what was missed) live in the new Feedback module: 📦 COMP #8: THE WILDCARD - The Vault 📚 WHAT THE FIELD TAUGHT Three lines split thirty-two repos: ✅ Enforcement. A must in a markdown file is a request. A must in code is a constraint. (That line is from one of your repos. It's in the package. Go find whose.) ✅ Evidence. The builds that shipped receipts of a REAL run transcripts, dated logs, before-and-after fixes read differently every single time.
Pinned
1d •
❗The Lyceum opens this Thursday: live webinar at 7 PM ET❗
Thursday, July 16 at 7:00 PM ET. Quick version for anyone who hasn't been following: The Lyceum is Eduba's 12-week AI certification program and the first credential we've ever issued. Over 3,000 people are on the waitlist and seats per cohort are limited. What we'll cover in the hour: 01 / The structure. 12 weeks, three sprints, nine live sessions, 18 hours of instruction, 12 instructors per cohort. 02 / The cohorts. Technical, Business, and Creator. Same core curriculum, weighted differently. We'll walk through how to pick yours. 03 / The competition. $250,000+ in prizes across the tiers and how your capstone feeds into it. 04 / The certification. What you have to do to earn it and what it actually certifies. 05 / The investment. What it costs, how payment works, and who should not enroll. Then live Q&A until the questions run out. One more thing. At the end of the session we're doing something for the people actually in the room. It's capped at a small number, it goes in the order people claim it, and we're not putting it in writing. Be there and stay to the end. The session is live only. No recording going out. Thursday · July 16 · 7:00 PM ET skool.com/live/XM7969jTG7L Come with the hard questions. Bring the skeptical ones too. That's what the hour is for.
5h •
My first ICM project: My workspace
I decided that it was time to graduate from using regular chats with AI to using Claude Cowork. When I saw ICM, the lightbulb came on for how I was going to implement it. My previous state was to operate in multiple chats, download artifacts to an unorganized Downloads folder, and my work output lived in several places. This helped me organize and gave me a way to structure my work around what I used AI for. Instead of thinking through a workflow, I took some time to reflect on which topics in my day to day life I tended to use AI for help with. Those became my root folders. Inside each of those folders are the types of work or the mental modes that I work with them on. As an example, some of my root folders turned out to be career, health, work, homelab, garden, etc. When I am working on a certification, each cert has a workspace in the career folder. If I generate an artifact to help with exercise, it goes to the health - fitness folder. I built a skill that scaffolds any new directories into the structure. The new folder gets a default AGENTS.md and CLAUDE.md file (just a redirect to AGENTS.md) created that maps the folder. I tune the rules. This has allowed my work with AI to shift from long chats to build context, into an interactive workspace where my prompts are simply the tasks and the category. The context lives in the structure. Claude knows which certifications I have, which ones I am working on, and why I pursue them already. It already knows which plants I grew in the garden last season and which beds they were in. It knows which apps I wrote with AI, what their function is and the URL of the github repo. I'm excited about what this opened up for me and looking forward to developing workflows using this system. I've got some specific ideas revolving around system administration and security tasks that I plan on working on. Hope this helps someone else. Start from where you are and look for one way to improve your current systems. Implement it. Repeat the process.
Mar 15 •
🏁 Foundations 2.5 Check-In
This one breaks down orchestration. Vote below, then pick one AI tool you actually use and tell us in the comments: can you identify which part is the model and which part is the routing layer around it?
Poll
715 members have voted
1-30 of 2,520
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
🔥
+1719
2
+1259
3
+1028
4
+930
5
+739
Powered by