Locked in for the next 5 days only. Ends May 5th at 10:00 AM EST. No exceptions. 🎉 Premium: $27 → $14/mo 🎉 VIP: $97 → $67/mo The closest you'll get to our original launch pricing. We're doing this because the community has shown up for us, and we want to show up back. 🤝 🔥 Already a member? Read this carefully. To lock in the new rate, you need to: 1. Cancel your current plan 2. Resign under the new price That's the only way the system can apply the new rate. We have way too many members for manual refunds, so we can't refund anyone who just signed up at current pricing. But the savings stack month over month, so if you plan to stick around (and you should 😁), the math works out fast. 🚫 A few ground rules: Please do not DM myself or Jake about pricing, exceptions, or extensions. We love you, but we're a small team and we need to stay focused on building. Everyone gets the same window. Everyone gets the same deal. If you miss it, you miss it. We'll do more things for the community down the road. ⏰ The clock: 🟢 LIVE NOW 🔴 Locks May 5th, 10:00 AM EST - Premium gets you The Vault and Afternoon Tea calls. - VIP gets you The Drawing Room, High Tea, and bespoke folder builds from Jake himself. If you've been on the fence, this is the moment. 🚀 Tag a friend who needs to be in here. Let's make Cinco a movement. 🎊 🌶️🌶️🌶️

Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.

If any of you have his twitter/linked in, totally comment and tell him to respond to my email. Want him to come chat with all of us and I think he would be happy to just need him to get eyes on, as someone who gets thousands of emails a day I would not be surprised if he never sees it even if it is valuable.

Quick note about Skool’s bot protection: If your comment is just a few short words, you’re better off hitting the like button instead. What you probably don’t know is that the admins are getting absolutely blasted with anti-bot warnings — and Jake didn’t do me any favors by blowing up my notifications. We’re growing extremely fast (25,855+ and climbing), so we’ve got a massive target on our backs. Short, low-effort comments are triggering the system hard right now.Help us keep this community high-quality: Only comment when you have real value to add — sharp insights, innovative ideas, or meaningful experiences. Likes 👍 are there for quick appreciation. Save the comments for stuff that actually moves the conversation forward. Do your part. Let’s protect the space we’re building together. Thanks, legends. *** @Jake Van Clief has not approved this message, he's swamped ***

So as some of you know, I posted yesterday about having an agent agnostic workspace. Here's a few learnings for those building out their workspace now, so that you don't have to spend a couple million Claude tokens porting your entire workflow like one gurl did. 😅 The trigger I spent a day rebuilding the foundation under every project I run. The orchestration layer behind everything I do, every product, every brand, every active client, sits in one root. Last week I moved that root. The move cost roughly two million tokens of Opus output, sixty-seven logged migration steps, and a purpose-built migration toolset. Worth it. Here's why I did it, what changed, and the structure I wish I'd started with. Why I did it The old setup grew. Months of layered decisions, each defensible in the moment, ended up nested three folders deep with the same name repeated in each. Not a typo. Three of them. The path was a symptom. The real problems were structural. Code, content, and config were braided together. Every workspace held source files, render outputs, plan documents, briefs, screenshots, and configuration in one tree. Backing up orchestration meant backing up renders. Reading briefs required mounting the encrypted code drive. Hardcoded paths were everywhere. Tools, hooks, plugins, and native apps all assumed one specific absolute path. One move would have shattered the system. The configuration was Claude Code specific. Hooks, settings, slash commands all baked into one agent's surface. If I wanted to run the same workspace through Codex or Gemini, the layer of plumbing I'd need to build was its own project. Session state and canonical config lived in the same directory. Ten gigabytes of accumulated runtime state in .claude/ made the workspace feel heavy. Most of it was regenerable. None of it was sorted. What changed The migration introduced three roots, each with one job. Workspace root holds orchestration only. Markdown briefs, YAML manifests, plans, decisions, content drafts, memory bank.