Welcome to Clief Notes. Here’s where to start. 👋 You don’t need to watch the entire classroom before trying something. Pick a starting point, make something small, and bring your questions back here. 🧭 Find your way around Navigating the Course shows you what’s here and how to get around. If you’re new to working with AI, start with The Foundation. We work through prompting, context, and organizing your files so you can give an AI a job you can actually check. You’ll find guidance for Claude Code and Codex, plus a regular chat route where you save the files yourself. 💬 Use the check-ins At the bottom of the lessons, you’ll find polls and discussion posts. Share what you tried, what worked, and what needed correcting. If something doesn’t make sense, post the lesson and timestamp. “I got stuck right here” is a perfectly useful question. 🏆 Put something into practice Visit the Competitions Mega Thread for the current challenges, rules, and prizes. It’s a good excuse to finish something and see how other people approached the same problem. 📦 Looking for more? Premium: Explore The Vault for practical packages, templates, meeting takeaways, and worked examples. VIP: Head into The Drawing Room for VIP sessions and resources. Post your work. Ask questions. Help someone else when you can. What are you here to build—or what’s one task you’d love to make easier? Tell us below.

@Pascal Pollack THE LEGEND put words to something I’ve had my mental finger on for a while and couldn’t quite put words to yet. https://www.skool.com/cliefnotes/what-can-we-build-together?p=36d66d76 PLEASE go watch his video, read the post and let us know how we, the Clief Notes Community, can help you and what you bring to the community. https://www.skool.com/cliefnotes/what-can-we-build-together?p=36d66d76 There is so much expertise and love in this community it’s unreal 🫶 https://www.skool.com/cliefnotes/what-can-we-build-together?p=36d66d76

🎁 $1,000 IN PLATFORM CREDITS🎁 One winner takes it. 📋 THE CHALLENGE Pick your weakest entry from any past comp. Read the feedback file we sent you. Rebuild it. Then prove the rebuild is better. Every entrant since the Cartographer has a file that says what worked, two fixes, and the one thing that would have moved them up. Most of those files have been read once. This week you act on one. This week's deliverable is the original pinned, the feedback file, the rebuild, and a control showing old against new. 🎯 PICK YOUR ENTRY Any comp you entered. Cartographer, Auditor, Translator, Control, or anything earlier if you still have the repo. Pick the one where the feedback file stung the most. That is the one with the most room. If you have never entered, you can still play. Pick any public repo from a past comp whose author has posted that it is open for rebuilds, and treat the public results post as your feedback file. Credit them in the README. A few sparks: - Your Cartographer map, rebuilt so the territory ships pinned in the repo - Your Auditor, rebuilt so every finding resolves to a provision a mod can open - Your Translator, rebuilt so the shape holds on the input that broke it - Your Control, rebuilt around the question the folder lost on - Any entry whose README a stranger could not walk The pattern is the same every time. The feedback named a gap. You close it and show the closure. 🔥 THE ANGLE THIS WEEK Last comp was The Control. You ran the same questions with and without a folder and committed both. The Rebuild runs the same test on two versions of the same folder. Original on one arm. Rebuild on the other. Same questions, same order. The questions come from the feedback file, so the test is aimed at the exact thing you were told to fix. In the Cartographer round, Adam put his README in front of an outsider, watched her fail for twenty minutes, cut it from 904 words to 471, and kept the old version in the repo so you could see the change. That is a rebuild with the receipt attached. This week everyone ships one.