User
Write something
New Member Onboarding. is happening in 2 hours
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
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.
Pinned
🌵 ANNOUNCEMENT: THE LEGENDS CLASSROOM IS OPEN 🌵
Gather round, Clief Notes crew — we’re opening The Legends: a classroom on the Frontier built around two gunslingers who deliver real systems, not hype. Each legend has a dedicated folder packed with signature builds, frameworks, and battle-tested wisdom. Start where the dust is thickest for you. 📐 Bas Rosario – The Wise Architect’s Library Master planner and blueprint boss. Bas designs for deep understanding and human–AI collaboration so you stay in control — frameworks, systems thinking, responsible AI, and work that still feels human. 👷‍♂️ Don Roy – The Master Builder’s Forge Hammer in hand, fire in the forge. Don turns ideas into working tools: automation, quality control, content systems, Remotion + AI builds, and anti-slop standards that keep what you ship durable. These two are the heartbeat of this classroom — grinding, growing, and lifting the whole crew. Your move: Pick a folder. Open it. Start forging. https://www.skool.com/cliefnotes/classroom/b5143824?md=61c684c877384eefbd11c804f83aac05 Who are you riding with first — Architect or Builder? Drop a 🤠 below and go make something that lasts.
🌵 ANNOUNCEMENT: THE LEGENDS CLASSROOM IS OPEN 🌵
I built a production line for these Skool posts. Here's how it runs.
Yesterday's voice guide post was the first thing off a line I'd built the same day. This post is the second. Build Log entry two, and the subject is the line itself. The problem it solves: I was treating this community like a scratchpad while treating LinkedIn like a stage. That's backwards. The how-to that actually moves my builds comes from here. So I gave Skool the same respect I give any channel I market on, using the machinery I already run for my own brand. What I built, in one session: 1. Made this community a client. My marketing factory now carries CliefNotes as a real engagement: intake, work orders, a sign-off desk, the same gates my brand gets. Not a metaphor, a folder with contracts in it. 2. Wrote a Skool channel playbook, the factory's ninth channel. Core finding: Skool is a community feed, not an interest-graph algorithm. Reach here comes from early comments and standing, not dwell-time tricks. The title carries the hook, and the first hour decides whether a post circulates. 3. Signed a narrative lane. Three stages: the practice (what I build), the proof (what ships), the validation (the Lyceum, journaled as I go through it). Every post has to name which stage it advances or it doesn't ship. Posts become a series instead of one-offs. 4. One command runs the line. I name the build; an agent gathers the evidence, loads my voice guide, the lane, the playbook, and every edit I've made on previous posts, then drafts. 5. Two gates before anyone sees it. A brand gate checks the draft against the signed rules, then I sign or edit. I paste the post myself. No API, no scheduler. 6. The loop compounds. My edits log to an append-only file. A correction repeated three times becomes a rule. A post pattern proven across three runs becomes a template. Credit: the folder-structure-as-agent-architecture method the whole factory runs on is Jake's ICM. I didn't invent the frame, I industrialized my corner of it. Yesterday's credit list stands too; this build sits on all of it.
0
0
Poll: What's In Your Toolbox?
Edited: 100+ have voted Results to follow Thank You Please take ten seconds to respond to this poll — it helps everyone see the real meta! I’ll like every comment. BONUS: If I can twist @Jake Van Clief ’s arm, we’ll pick one random commenter for 1 month of premium access — for free once we hit 100+ votes! Vote and reply! Main method you use for interacting with AI agents right now? WHAT"S IN YOUR TOOLBOX RIGHT NOW?
Poll
151 members have voted
Poll: What's In Your Toolbox?
1-30 of 2,737
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