User
Write something
Pinned
START HERE
Glad you made it in. Before you go anywhere else, work through the steps below. They will get you set up and ready to start. ✅ Introduce yourself in the comments. Tell us what you do and why you are here. ✅ Watch the Getting Started overview 📚Navigating The Course - Getting Started · Clief Notes ✅ Start with the Foundation course 0.1: Where All Of This Leads - The Foundation · Clief Notes ✅ Fill out your profile so people know who you are ✅ Join the next competition ⭐ Competitions Mega Thread - Getting Started · Clief Notes ⭐ On Competitions (and why I love them) We host a competition every two weeks. These are some of the most powerful places to learn and build here. Also Cash prices (often over $200) for the winners. Learning how to do something is one part of it. The real learning starts when you put it to work. That is what the competitions and the build sessions are for. On top of this they act as a portfolio a place to not just show us but show others (clients, bosses, your best friend) what you have been building and that you really CAN build. In order to win a competition you must be a paying member (It takes me hours to review submissions sometimes days. But if you win ONCE you can pay for a whole year of membership so I think that's only fair!) Watch the videos, then go make something.
START HERE
Pinned
I built a custom browser extension to browse CliefNotes
Browsing on Skool can be a bit overwhelming with it's UI (my eyes need a dark theme) and the great volume of stuff on CliefNotes makes jumping in daunting, especially if you're away for more than a day, so I wanted something that made browsing feel effortless and easier to navigate and see things and keep posts around that I wanted to dig into a bit more. So I built a browser extension that gives me a faster, cleaner view over the same Skool feed, posts, and comments. The catch: I don't know web code. I don't know APIs. But I've learned that knowing what I *don't* know is exactly where AI earns its keep. I know how to troubleshoot — so I can tell it what's happening, what's breaking, what information I need next — and it hands me the technical roadmap I don't have. I wasn't writing this thing so much as steering it. The part that nearly broke me was comments. A post with over 100 replies would render only 50, and I couldn't see why — Claude almost threw in the towel but I persisted because one thing I've learned working Game Dev is that if you can see something on the screen then that data exsists somewhere, you just have to figure out where to look. The takeway I want to flag is to think about pointing AI at your pain points, the best things to come out of using ai for me have been asking "What if?" And a lot of the amazing things people have created in here follow the same pattern. I also want to highlight this post by @Jason Jennings : https://www.skool.com/cliefnotes/sortable-posts-clief-notes-sidebar-easy-copypaste I was in the middle of my build when I came across it and I folded some of the sorting options into the extension because I thought they were great I built it to be shared — open source, free, and I'll keep updating as I go, genuinely open to suggestions. Only caveat is it can only do what Skool's API allows. Also I use Firefox mainly and it's easier to sign a native browser extension for firefox so you can install directly using the .xpi link in my repo, for Chrome you'll have to download the .zip and in Chrome set it to developer mode and you can sideload an unpacked extension (instructions should also be in the zip).
I built a custom browser extension to browse CliefNotes
Pinned
🎆 THE LAST SALE EVER — HELP US GET TO VEGAS 🎆
🎯 WE READ ALL OF YOUR RESPONSES. HERE'S WHAT'S NEXT (AND A BIG ASK) A couple weeks ago we asked you what you wanted Clief Notes to become. You showed up. You wrote real, thoughtful answers, some of you wrote essays. We read every single one. Twice. So before anything else: thank you. This post is us answering you. 💬 YOU TOLD US. HERE'S WHAT WE'RE BUILDING. You said you want a clearer path from learning ICM to actually getting paid for it. → It's coming. A real learning-to-earning track, plus a talent platform we're building to connect you with people who want to hire what you can do. Heads up: the talent platform will be Premium and VIP only, one more reason to lock in below. You said competitions without feedback don't help you grow. → Fixed. Going forward, every single entrant gets tailored feedback on their build, not just the winner. We're moving to two competitions a month so we can do it right. And both monthly winners get a 30-minute call with me. You said the best builds get buried in the feed. → We're building a tagged library so you can actually find "ICM setups for solo operators" or "small team, non-coder" instead of scrolling for an hour. You said you couldn't map all the pieces, Skool, Discord, the Lyceum, ICM, what each tier unlocks. → A single orientation page is on the way. One place that breaks all of it down so nobody's lost. You said you want to connect with each other. → We hear you. Meetups, pairing, and a recorded "After Tea" hangout are on the table. South Florida alone has over 1,000 of you. Let's use that. You said we've felt spread thin. → The most honest one. You're right. We're bringing on real help to run the day-to-day so the community gets consistency, and so Matt and I can keep building the things above instead of dropping balls. You called it, and we're fixing it. 📍 QUICK NOTE ON ICM: a few of you asked for "ICM with Copilot" or "ICM with n8n, Sheets, GoHighLevel." Good news, ICM already works with any model and feeds straight into the tools you're using. It's the structure underneath all of them, not a separate thing you have to relearn per tool. If that's not landing for you, that's on us to make clearer, and we will.
Streamlining my work with Antigravity and ICM.
Oh boy, I am a happy camper . I downloaded the paper on ICM and converted that into an .md file. Just for fun I also downloaded the README.md from the github repository. Than asked Antigravity to read these two files and do an audit om my filestructure based on the information in the two .md files. It gave me excellent feedback and wrote an implementation plan to rearrange the file structure to be fully compliant, reorganized all the files and either edit or create the relevant files. He also created an agents.md file in its configuration section that tels Antigravity to read the claude.md files for instructions. After all that work I had it do an audit again and everything was OK. Including the .md file that holds the templates and file structure that i to use when I need to create a new client. It took while for this proces but now I am ready for working with this system which will save a ton of time, I expect. This of course was necessary work for the next step, which was to have Antigravity sync the complete development structure for a website, I was building for a client, from my development server to my laptop, had it do an audit on the code, made some suggestions which I accepted, Antigravity again wrote an implementation plan that I reviewed and accepted, after a few changes and then had it deploy the website environment to my hosting server . After resolving some issues the site is now in the test area. Now the only thing I need to do is refine this whole process so that I can automate these steps and have Antigravity do audits on my development work and when ready for test, deplot it directly to me test server online for the client to test. All this took me about half a day. Hours well spend, so that now the structure and procedure are there in place I can focus on development and have the rest basically automated (supervised for now). BTW I develop websites using the Django framework and python scripts and occasionally wagtail. The ICM system keeps me and Antigravity organized and I can easily do handoffs and pickups .
Streamlining my work with Antigravity and ICM.
🗺️ Afternoon Tea #9 from last week is in The Vault
Recording's up, and I packaged the whole thing so you can drop it straight into your second brain or hand it to your AI. 🍵 Here's what we got into this session: 🧠 Map your work, don't just store it. A second brain holds notes. A map holds your work plus the people and data around it — teams, processes, and the links between them. You can't improve what you can't see, and neither can your AI. 🔗 Every workflow is a node. One markdown file = one process. The references between them are the edges. That's the whole graph. 🟢 Build workflows, not outputs. Store the outputs inside the workflow. Then when Opus 4.8 or Fable ships, the right feeling is "cool, my system just got better" — not scrambling. 🔍 Google basically proved the method. Their new Open Knowledge Framework (dropped June 12) is markdown + files + front matter to document and query big datasets. One of the biggest players outside Anthropic is doing the markdown-and-files approach we've been practicing here. 👀 🏛️ Plus: mapping a real company's teams in Obsidian, the platform coming so you can own and license your workflows, and a sneak peek at my new paper — Human in the Compute Layer — built on Engelbart's 1962 work. 📎 What's attached (and what each file is for): 📝 session-notes.md — The opinionated version. All the ideas from the call, written so you can act on them. Start here if you want the short version. 📚 term-sheet.md — Plain-English definitions for every term: node, edge, semantic layer, OKF, ICM, "the data becomes the agent," and more. Perfect if you're new to the room. 📄 vault-page.md — The index for the whole package. 🗂️ Package.zip — Everything zipped, ready to add to your AI's memory (Claude, Hermes, OpenAI — whatever you run). 💬 Watch it, grab the files, and drop your questions below — the best ones seed the next Afternoon Tea. So much love. 🫶
1-30 of 2,084
Clief Notes
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)
Powered by