Pinned
👑
⭐
26d •
Welcome to Clief Notes. Here's where to start.
1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. 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 join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?
Pinned
👑
⭐
4d •
What do I read?
Despite all the ai hubbub and second brains someone asked what I read and IF I read at all anymore. The answer is most certainly YES. You can make connections that might be missed by a million questions with AI by diving into books and reading your self. Some books may not even have most of their pages on the web especially older ones and those are often my favorite. Here are 4 of my current favorite readings to prepare me for the future (by looking at the past) 1. Mythical Man Month (1972 by Fred Brooks) 2. Psychology of Computer Programing (1971 by Gerald M Weinberg) 3. Augmenting Human Intellect (1962 Douglas Engelbart) 4. The Creative Act: A Way of Being (2023 by Rick Ruben) Rick Rubens book is just great in general for business and creative acts.
Pinned
1d •
Community Guidelines
This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post. 5. No spam, no pitching. Sharing a tool you actually use and explaining why you use it is fine. Dropping a link with no context, cold DMing members, or treating the feed as a lead list is not. Networking is genuinely welcome (there's a Connection Hub for exactly that: https://www.skool.com/cliefnotes/new-the-connection-hub-is-live) but networking and pitching are not the same thing, and everyone can tell the difference immediately.
2d •
Why AI won't make you rich in 2026
Some in this group with too much time on your hands and have had some illness or disorder for not just reading but also commenting on my posts, have her me say more than once that that Jake is the Alex Hormozi of AI. Third-row, foam-finger, "just one more video at 1 AM while the whole house is asleep" levels of fandom. Then the ACTUAL Alex Hormozi drops a video titled "Why AI won't make you rich in 2026." https://www.youtube.com/watch?v=WttZ6b-KUP4 I clicked in with my chest out, ready to defend the family honor. Nine minutes later I'm sitting there like a kid who just found out Santa outsources and the tooth fairy are just the people who spawned you. Because the man's right. Dangit. His whole case, no chaser: AI is leverage. Real leverage. But it didn't repeal every OTHER kind of leverage that was already minting money before ChatGPT learned to talk. Capital. Media. A team. A sales process that actually closes. An offer that doesn't stink. AI showing up didn't delete a single one of those. Then he drops the part that made me put the cigar and whiskey down. (La Aroma de Cuba Mi Amor and Noah's Mill in case you're wondering what to send me on my birthday). He asked his richest, oldest friends how much they personally touch AI in a day. Off camera, the honest answer was basically "bro, I don't." Their teams do. They don't. The guys with the yachts, gently breaking it to the AI guy that the robots aren't driving the boat. And this is where it kicks those of us who LIVE in this stuff square in the tokens. (I laugh at my own jokes, even when they're in writing, you gotta admit, this one was funny). He says most owners have AI-maxed their capacity, so now they crank out more, faster. Except the extra stuff they're automating was the low-priority junk. So we've built a gorgeous machine that does the wrong thing at the speed of light, and we're out here refreshing Stripe wondering why it's so quiet. His punchline is the one I want tattooed on the inside of my eyelids: the highest-leverage move in a business is making good decisions. Higher leverage than AI. Deciding what NOT to do. He said it's more efficient to decide something isn't a priority than to automate something that isn't a priority. Go ahead, read that twice. I did, out loud, to nobody in particular. And here it is again in case you didn't actually go back to read it.
22h •
Git Repo Security Skills
Stop README-shopping. Start scoring the repos you actually trust. Most of us still pick open-source like restaurants. Stars. Nice README. Maybe a glance at the last commit. That friction is real, and it's how vibe-coded slop ends up in the stack. New classroom piece is live: Git Repo Security: Why It Matters, and How We Actually Do It https://www.skool.com/cliefnotes/classroom/c7f102c7?md=43a45577d5cb4096b040770491d87b50 Why this hits us: we pull public git constantly. Agents clone third-party skills. Volunteers don't have an AppSec team. Stars are a weak signal. The article folds OpenSSF / SLSA / CISA-style checks into two portable skills so the discipline gets cheap and repeatable. How you run it (newbie path) 1. Open the article and download the zip. 2. Drop the zip into your harness (Claude Code, Cursor, OpenCode, Grok, etc.). 3. Prompt the agent like a colleague: run repo-scorecard Egonex-AI/Understand-Anything (github username/repo) or run repo-eval Egonex-AI/Understand-Anything ============================================================= Here's what you get from repo-scorecard: Scorecard: Egonex-AI/Understand-Anything Score: 9.50 / 10.00 — healthy, well-run project What's good: • Actively worked on — last update was yesterday. • Very busy recently: 355 commits in the last 90 days. • Many people involved — about 70 different contributors this year (though one person still does most of the commits). • Has a clear license, a README, and a security contact policy. • Has automatic quality checks and tests set up. • Ships tagged releases (8 tags) and keeps a fixed parts-list for its building blocks. Things to know: • No automatic updates for the building blocks it depends on. Score based on publicly visible project activity and housekeeping. It does not include a security scan of the code itself. ==============================================================
1-30 of 2,700
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
+1422
2
+1217
3
+686
4
+611
5
+559
Powered by