User
Write something
New Member Onboarding. is happening in 6 days
Pinned
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
ATTENTION CLIEF NOTES COMMUNITY MEMBERS
Sonija Quinn here — one of the admins working behind the scenes to help run the Clief Notes community. We’ve been made aware that some members are receiving emails from noreply@skool.com stating that their Clief Notes membership has been cancelled or that they’ve been removed from the group. Others have noticed their VIP or Premium access suddenly disappear. We want to get ahead of this and address it directly. First and most importantly: No admin at Clief Notes has removed you. You are not banned, you are not in trouble, and you have not broken any rules. This issue is occurring on Skool’s side, not ours. One of our members contacted Skool and was told that a new platform update is causing unexpected disruptions. We’ve just been made aware of it, and we are actively working to resolve. If this has happened to you, please DM me directly on Skool with: - The email address associated with your Skool account - The tier you should be in (Premium or VIP) - The notification email you received - Any screenshots that may help - That’s all I need and will follow up accordingly with each of you that DM’s me. I will be the single point of contact for this issue, so there’s no need to message other admins. Please send this information to my DMs, not the public feed — your account details shouldn’t be posted publicly, and I can resolve things much faster through direct messages. If you’ve already posted about it, no problem — just send me a DM as well so it doesn’t get overlooked. If this hasn’t happened to you, there’s nothing you need to do. Just keep this post in mind. If you do receive one of these emails, you’ll know immediately that it’s not legitimate and not coming from us. We truly appreciate your patience while we work with Skool to get this sorted out. Thank you for being part of Clief Notes — and please accept our sincere apologies for the inconvenience this is causing.
Pinned
Community Guidelines
This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post.
I gave this presentation to over 150 people last night. Turning daily notes into content streams.
I gave a short look into how my content engine works at an event in West Hartford last night. Even met up with a couple of folks from this community there! Was a great night and awesome to have the chance to connect with folks doing some of this stuff and talk up this community. If you enjoy the presentation please leave a like and subscribe to help me keep growing this thing!
🛠️ 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. 👇
1-30 of 2,779
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