User
Write something
High Tea is happening in 6 days
Pinned
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). 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, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
6517 members have voted
Pinned
🇬🇧 GOOD MORNING FROM LONDON! 🇬🇧
Jake and I made it across the pond. We're here for London Tech Week all week. We got invited out for this one, which still feels surreal to type. We've got multiple pitch slots in front of investors over the next few days to talk about what we're building at Eduba and where this community is headed. Big moments lined up. Big rooms. Big swings. 🚀 If you're at the conference, DM me! Would genuinely love to meet anyone from the community in person. We'll be all over the Techscaler booth and floating between sessions. Even if it's just a hello and a handshake, hit me up. 🙏 And if you've got a second, send some good energy our way this week. We're about to walk into some rooms that could change the trajectory of what we're building. Wish us luck. Light a candle. Whatever your version of that is. We'll take all of it. Now to the real reason you're here. 👇 ---- 👇 🏆 7-DAY LEADERBOARD WINNER: @Bas Rosario 🏆 🔥 Bas just won it AGAIN. Back-to-back. Last week he won as a Premium member and we converted him to free Premium for life. This week he's already Premium for life, so we're bumping him up. ✨ Free VIP for life. ✨ The Drawing Room. High Tea. Bespoke folder builds with Jake. All of it. Forever. No charge. ---- ⏰ The 7-day clock just reset. Next Monday we crown the next winner. Could be you. 🎯 How it works: - 📝 Post bad ass stuff - 💬 Help people in the comments - 🛠️ Share what you're building, what's working, what's breaking - ❤️ Engage with other members' posts The leaderboard tracks all of it. Whoever sits at #1 next Monday wins. ---- 🎁 The prize, depending on where you're at: 🆓 Free member? You get lifetime Premium, free ⭐ Already Premium? We convert your Premium so you stop paying 👑 Already VIP? We convert your VIP so you stop paying Either way, you stop paying. Forever.
Pinned
🏆 WEEKLY COMP #7: THE OPERATOR 🏆
🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇬🇧 We're back. Good morning from London. 👋 Thanks for the patience last week. Jake and I needed a few days to breathe before London Tech Week kicked off, and you all responded with nothing but support. We don't take that for granted. Now let's get back to building. ---- 📋 THE CHALLENGE Build a folder-based AI operator that handles ONE operational workflow end-to-end. You pick the workflow. This week's deliverable is one operator folder that someone could drop into a Claude project and use to handle a real business workflow without babysitting. ---- 🎯 PICK YOUR WORKFLOW The workflow is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎫 Customer support triage (which tier handles this ticket?) - ✅ Content review and approval - 📨 Lead intake and qualification - 💸 Refund request handler - 🤝 Partnership pitch evaluator - 🎙️ Podcast guest pitch sorter - 💼 Freelance project intake - 📄 Resume screen for one specific role - 📅 Meeting request triage (book, decline, delegate) The more specific, the better. "Customer support" is too broad. "Refund request triage for an ecommerce store doing under 200 orders per month" is right. 📎 If you want a fully written client brief as a reference, the attached PDF walks through one example. Don't build the example. Use it as a template for how to think about scoping your own operator. ---- 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your operator is a folder with five things: - 📄 identity.md (who the operator is and what workflow they own) - 📐 rules.md (the decision logic: criteria, edge cases, escalation rules) - 💬 examples.md (decisions in action, including at least one edge case) - 📚 reference/ (checklists, templates, rubrics) - 📖 README.md (how to use it)
Hi everyone! 👋
I'm Karli, Bas's wife. I just joined the community and wanted to introduce myself. If you've spent any amount of time here, there's a good chance you've seen Bas around. He seems to be everywhere. 😂 The good news is you don't have to worry about me posting nearly as much as he does. He does enough talking for both of us. And for anyone wondering: yes, he is exactly the same in person. In all seriousness, I have to give Bas credit for encouraging me to explore AI. Years ago, he told me I was way ahead of the curve when it came to AI and that I had a way of communicating with it that just made sense. He always said I was naturally good at prompting and getting great results, and honestly, that's a big part of what inspired me to learn more about AI and pursue it further. I also come from a graphic design background, and as someone who's neurodivergent, I've found that AI complements the way I think, learn, and solve problems. By day, I'm a hairstylist and educator in Southern California. I've been behind the chair for over a decade, specializing in international hairdressing with a focus on dimensional low maintenance hair color, and textured razor cutting. AI has become an important tool for me both professionally and personally. I use it for brainstorming, client communication, marketing, content creation, education, business planning, and learning new skills. The thing I'm most excited about right now is that I'm building an app for hairstylists. I don't come from a software development background, so it's been a huge learning experience, but AI has made me realize that building something like this is actually possible. I'm here to learn more about Claude, Claude Code, AI-assisted development, and to connect with other people who are exploring what these tools can do. Looking forward to learning from all of you!
This is how we do it
Most people are learning prompt engineering The real opportunity is workflow engineering. Prompts get outputs. Systems get outcomes.@amanbuildss ICM is our system
1-30 of 1,641
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by