User
Write something
Afternoon Tea is happening in 5 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
5518 members have voted
Pinned
🏆 WEEKLY COMP #4 RESULTS: THE AGENCY 🏆
I thought last week was hard to judge, This was the hardest comp to judge so far. Not even close. Picking the top five took longer than picking the winner. Working apps. Animated explainers. Voice acting. Full Instagram brands. Three-contract architectures. Cloud automation that actually runs. People showed up this week. Before I name the winners, I want to be honest: this was tight enough that a few of these slots could have gone the other way. The gap between 1st and 5th was smaller than the gap between 5th and the rest of the pack. Let me run through the runners up first. ➖➖➖ 🎯 @Daniel Neuhaus 🔗 Repo: https://github.com/Six8Coffee/diana-calloway-real-estate-ai 🌐 Team portal: https://six8coffee.github.io/diana-calloway-real-estate-ai/ The only submission with real automation wired up. Two Cloud Routines running on Anthropic's servers. One processes the leads@ inbox hourly via Gmail MCP. The other sends a daily team briefing at 8am. Plus a hosted team portal, a confidence-and-trail audit log on every handoff, and a 6th specialist (Nurture Coordinator) for leads that aren't ready yet. The "Jordan's day-one guide" framing in the README addresses a named hypothetical new agent and walks through the three daily tasks concretely. Real Austin context (Mueller neighborhood, 512 area codes) shows attention to brief details that a lot of submissions skipped. ➖➖➖ 🎯@Sean Vargas 🔗 Repo: https://github.com/InsightfulMinds/cold-start 🌐 Live page: https://insightfulminds.github.io/cold-start/ Best diagrams in the comp. Best single-page packaging. The presentation is the most readable explainer of any submission this week. If you want to see how to communicate an ICM system clearly to a non-technical reader, study Sean's page.
Pinned
I come asking for help! (NEW ROUND! VOTE ONCE A DAY PLS)
Because of the Amazing support you all gave for the first Round Wylder (my step daughter) made it into the second round! You can vote once a day and some days are 2x votes ! I would love love love if any of you support her going to work with some of the best animal rescues in the world to just cast at least one free vote if you can! You can vote here! Not Ai related so sorry for that ! Wylder | Junior Ranger
New Video: We Audited a Vibe Coded Production App. Three Holes Found.
Dropped a new one for you all. Mike from Urban Pulse let me share footage from his security audit. He vibe coded his whole platform using my routing architecture, then hired me and my team to read every line before he opened it up to high ticket clients. We took our time over many hours. We found three holes that I share here. A Google Maps API key that had already been flagged and locked down by Google. A second cryptographic auth layer the AI built on top of Supabase, which already handles all of this for you. A JWT verification step that never checked the issuer, meaning any valid Supabase token from any project on the internet would have passed. This is what real building and shipping looks like in the AI world. Mike built something that used to take a year and a couple hundred grand. He did it solo. Then he paid engineers to audit it before any customer touched it. Copy his move. If you are vibe coding anything you plan to put in front of paying clients, watch this one.
vibe-code-rules.md
So I haven't had the chance to dig into the classroom yet so I'm not sure if this is covered anywhere.. but this is my set of general vibe coding rules that I have been working on to use across all projects. This way I have a single "source of truth" for best practices to include on all builds and try to keep things clean. So far it has been working pretty well (from an amateurs perspective haha) and looking forward to stress testing it more. Please take it and use it for yourself if you don't have anything similar yet. Also, I would really appreciate any feedback from the more experienced devs/engineers in the group. 🙏 Edit for clarity: this doc is something I have been applying to all vibe coding projects. Not all projects in general. Another edit for clarity: I am just getting through Jake‘s ICM paper now along with the classroom material. I was not aware that he also refers to the claude.md as a global file to be handed off to the highest level orchestrating agent. This global.md would be better named something more specific and placed around layer 3 of the workflow (someone please correct me if I’m wrong). Anyways, hope this clears up any confusion there may be. Decided to change the name to vibe-code-rules.md for clarity =)
1-30 of 1,229
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by