User
Write something
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
6059 members have voted
Pinned
🫖Afternoon Tea 5 is live on YouTube
Sixty minutes of real questions from real builders. Rich asked what skills to learn to stay competitive in AI roles. That answer became the frame the whole session ran on. From there we worked through finding clients, content strategy, the HTML versus markdown question, and what to build next when the obvious automations are already running. Natalie took the spotlight slot. The session closed on why liberal arts is the durable layer when most technical work gets absorbed by the next platform release. A few things you'll hear if you watch: - The L1 to L3 effort ladder, with the Pacific Life over-engineering story - The 200 to 48,000 YouTube subscriber path with zero ads and zero outreach - How the Feeld engagement came from a CTO finding the channel organically - Tokens as coordinates and what the Anthropic engineering team was actually saying about HTML - The four-year test for what stays durable in your stack The three questions at the end are the homework. The third one matters most. 📚 For Premium members The full artifact package for this session is in the Vault: 🫖 Afternoon Tea 3 - The Vault · Clief Notes🫖 - The twelve-slide Decision Map deck (PowerPoint) - Three strategy markdown files: Effort to Output Ladder, Show Your Work, Productionize Your Opinion - A Term Sheet covering every piece of jargon from the call - The Vault module page that ties it all together The strategy files are built to paste into Claude alongside the transcript so you can apply each frame to your own work. That is the part the video alone cannot do. If you are on the free tier and any of this sounds useful, Premium is where the artifacts and the live sessions live. Twenty-seven a month. Biweekly. No pressure either way. The YouTube content stays free and stays current. Build something this week.
Pinned
⚠️ HEADS UP: PHISHING ATTEMPTS IN THE COMMUNITY ⚠️
We've noticed people sending out phishing links in DMs and comments. Quick PSA to keep everyone safe. ---- 🛑 THE RULE If someone you don't recognize is sending you links, asking for money, asking for login info, or telling you to "claim a prize" outside of an official competition post, it's not us. Don't click. Don't reply. Just delete. ---- 💰 HOW WE ACTUALLY HANDLE MONEY We will never send you money out of the blue. The only time you'll hear from us about money is if you've won a competition. When that happens, Sonija is the only person on our team who will reach out to collect your payment info to send your prize. If anyone else DMs you asking for payment details, banking info, or "verification" to release a prize, it's not us. Report it!! ---- 🚨 IF YOU GET A SUSPICIOUS MESSAGE 1. Don't click any links 2. Don't reply 3. Screenshot it if you can 4. Send the screenshot to Jake, Matt, or a mod so we can deal with it We're going to keep this community a safe place to build and learn. Thanks for looking out for each other. 🙏
Pressure-testing an ICM-adjacent idea before building
QUESTION FOR BUILDERS: Where does your workflow context live today, and what breaks first when you try to reuse it or hand it to someone else? I am especially interested in cases where the workflow works for you personally, but would be fragile for a team. PROBLEM: Folder-based AI workflows work well when one person understands the context. They run into challenges when you add collaborators and when the context becomes stale, scattered, unowned, or difficult to hand off. SOLUTION: My idea is to use Airtable as an ICM context registry that helps AI & automation workflows access context that's approved, current, and usable, without copying every source doc into Airtable. Canonical files stay in source systems / formats, i.e. markdown folders, Git repos, Google Docs, Drive, CRMs. Airtable tracks the operational layer around them: - pointer to the canonical source - owner - freshness or expiry status - approved context packs - review or readiness gates - workflow run evidence - source improvement requests when something is stale, missing, or conflicting - Airtable AI automation steps and field agents help classify, summarize, route, or draft context updates (review-gated) BENEFITS: - Teams can see which context is safe to use without digging through every folder or doc. - Source files stay canonical, so Airtable does not become a duplicate source of truth. - Context gets an owner and review cadence instead of quietly going stale. - Workflows can be blocked or flagged when required context is expired, missing, or conflicting (enforce at code / automation level). - Run logs create evidence of what context was used for a workflow output. - Source improvement requests create a feedback loop: when the workflow breaks, the source can improve instead of only patching the output. - Non-technical collaborators can participate through Airtable interfaces without needing to understand the whole file structure. WHY AIRTABLE? I'm a certified Airtable builder, so it's a natural choice for me. It's a strong place to track ownership, freshness, approval status, workflow usage, and follow-up requests. Airtable can provide:
0
0
Pressure-testing an ICM-adjacent idea before building
Who's here? Drop your intro.
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.
1-30 of 1,391
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by