Pinned
Mar 15 •
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
6147 members have voted
Pinned
👑
⭐
1d •
Phil Randazzo joins me live Tomorrow
Friday, May 29th, 12:00 to 1:30 PM EST, right here in Skool. Phil founded American Dream U back in 2003. It's a nonprofit that helps service members and their families land on their feet after the uniform comes off, whether that means a civilian career, more schooling, or starting a business of their own. They've worked with more than 16,000 veterans and brought in real entrepreneurs and business leaders to teach and mentor along the way. The man has spent two decades on this. I served. I know how strange those first months out can feel. You go from bouncing between countries, cracking dark jokes with people who have suffered with you, to classrooms or offices with blank stares and a lot of well-meaning advice that doesn't quite fit. Phil built something for exactly that gap, and he has watched thousands of people walk through it. We're going to talk about his own move into entrepreneurship, how to think in systems instead of one-off tasks, and where AI is opening real doors in the economy right now. Come with questions. This works best as a conversation, not a lecture. If you're a veteran or you're getting close to your transition, bring the thing you're actually stuck on. Phil and I will both take a crack at it. If you know someone who's transitioning and not in here yet, send them the link. Worth their time.
Pinned
2d •
⚠️ 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. 🙏
1m •
Keeping Up With AI ⌚
Someone made a comment in a post last week about something their friend said that keeping up with AI is for people who are unemployed. I will modify that with its for people who are unemployed or its their full time job. Just trying to keep up with the news and develop stuff is a full time job in and of itself. LOL I don't got the bandwidth to keep up with everything! I need to win the lotto or something so I can devote the time I want to do it.
1
0
5h •
Called out by a meme ...
This started with a meme on LinkedIn of all places... Not a whitepaper. Not a strategy doc. It irritated me because it named a thing I had been running into over and over. I would be building something with AI, the demo would look fine, and then I would hit a bug I could not even describe correctly. I would literally have to ask an AI: "What the fuck am I fighting right now?" Then the answer would come back with a name: "That is a CORS issue." "That is a race condition." "That is an auth boundary problem." "That is a missing migration." "That is row-level security." The useful part was not just fixing the bug, it was learning the thing had a name. That happened enough times that the meme started feeling like a map. So I took it seriously. I fed it into two different AI research tools and asked them to expand the idea. What do new builders miss? What breaks after the happy path works? Which layers matter before anyone treats an AI-built app as real? Then I took that research into Codex and started building CheckYourself. The name came from Ice Cube's "Check Yo Self," the line I could not stop hearing in my head: Check Yourself Before You Wreck Yourself. It was a joke, a rap reference, and eventually the product spec. Funny enough to stick. Blunt enough to be useful. CheckYourself is a free, local-first production-readiness system for AI-built apps. You drop it into or next to a project, point your coding agent at it, and ask for a read-only diagnostic. It does not start by fixing. It starts by mapping the app, inferring the stack, sweeping the production risk surfaces, giving the project a 0-100 Production Reality Score, and proposing the safest first fix batch. The rule is simple: Do not let the agent touch code until it can explain what it found, why it matters, how to verify the fix, and how to roll it back. I dogfooded it on itself before making the repo public. Final pass: 100/100, high confidence, complete 20-surface coverage, zero open P0/P1/P2/P3 findings.
1-30 of 1,425
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
1
+999
2
+844
3
+703
4
+695
5
+694
Powered by