The feed is a terrible index. Clief Notes AI is the librarian for it — not a second Claude, not a folder-builder, not a replacement for a Check-In. Free is three prompts. Total. DMs and the sidebar both count. After that you’re back in the classroom, which is still where the work lives. I wrote the map so you don’t spend shot one on “what can you do?” What’s in it - What this agent is (and what it will never do) - Chromium install, Student portal, same email as Skool - Three Getting Started shots and three Foundation shots you can paste - How to talk to it with the five-part prompt so a sloppy ask isn’t 33% of your budget Do this now 1. Classroom → Getting Started → watch Navigating The Course (2:51) 2. Open How to Access your Clief Notes Agent & Roadmap and install 3. Read the guide: Comprehensive Guide to Clief Notes AI https://www.skool.com/cliefnotes/classroom/c7f102c7?md=144082eaf875446eba04fa1db90fcc90 4. One DM. Then open Foundation 1.1. Check the box. The agent is a map. Your folder is the architecture. If the agent writes the system, you didn’t learn the system. Paste this if you only have one shot left: I just joined as [beginner / daily AI user / developer]. Give me the three-step start, the first Foundation lesson title, and what “done” looks like. Do not invent a custom curriculum. If three shots already feel tight, that’s the product working. Foundation stays free. Paid keeps the librarian on.

Has anyone tried to apply the folder structure learned here into their obsidian vault? Clief folder architecture really helped with retrieval and how knowledge is linked, this new meta really documents my current understanding on various subjects very well, in claude code sessions i don't have to explain as much context as before because claude code "knows" what i mean even better because of obsidian vault, but i realized that there needs to be a naming convention that works with clief folder architecture to make it truly optimized Anyone have any suggestions as to how to set up the naming convention?

Finished Playbooks 1.1. I decided to use the "Script → Spec → Build → Render" workflow to try and explain the workflow itself. The biggest thing for me was realizing the code really doesn’t come first. Once I had the script and visual spec figured out, the build became way easier to direct and refine. The hardest part for me was trying to make too much happen at once visually, especially in the refine section. Once I started separating each idea and letting the visuals happen in sequence, it got a lot cleaner. I ended up taking the Remotion render into CapCut and finishing it with the voiceover, music, sound design, pacing, and subtitles. This was my first real run through the whole workflow, and I definitely understand it differently now that I’ve actually built something with it. Which part of this workflow has been, or looks like it’ll be, the hardest for you?

Hey Clief Notes fam! 👋 I'm working my way through the new AI system and seeing what it can do. I've already posted about myself here when I first joined the group but I can most certainly add new info here. Once upon a time I knew nothing about ICM, now I have 3 whole systems that I've built, and while they may not be perfect (yet) they work and every day they get better. The best part though, is that I'm now able to show others how it works and they're benefitting too. I just asked the AI how to create a github repo (and it gave me some pretty clear instructions) and that will be my next mission. Onward and upward.

@Eugene Seva and I jumped on a video meet after I commented on one of his posts. He shared the GitHub repo of his work with me. A cool build of a Japanese digital business card for realtors. QR code, AI chat, mortgage calculator. Live site, paying customers, 140 merged pull requests, still shipping daily. Good build. I spent the day trying to work out the Western version. Never got there. What I got instead was better. That product works because the company behind it is a Tokyo brokerage sitting on 4.5 million sales records and 6,000 new listings a day. The app is a skin over a filing cabinet they already owned. Take the data away and it's a link-in-bio page with a chatbot attached. In the US that data is MLS-licensed per organization, and you need a contract with each one even going through an aggregator. That's a funded-company problem, not a weekend one. So I went looking for something that runs on nothing licensed. Six shapes, six walls. Business cards lose to a free tier with 150,000 reviews. Valuation needs an AVM license. Chat and nurture is held by people charging $395 a month. The fifth one nearly got me. Since 2024, buyers sign a written agreement about agent compensation before touring a house, and everyone is confused by it. No tool exists. I had the whole thing designed. Then I checked whether a real estate agent is permitted to explain a contract to a client. They are not. That's unauthorized practice of law, in all fifty states, and it's the agent handing the document over who carries the exposure. Insurers started writing generative-AI exclusions in January, so it wouldn't be covered either. Here's the part you'll care about. The constraint ended up as the folder structure. "Never produce client-addressed output" is a rule, and a rule sitting in rules.md is a suggestion. So it's also a check script. It reads every skill file, and if a client salutation turns up in one, it exits 1. Same for listing data. Each skill declares its inputs in a table, and the check fails if any input is a source we can't legally touch.