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
5029 members have voted
Pinned
🏆 WEEKLY COMP #3 WINNER ....
Before I get to the who and why, I want to say this plainly. Picking a winner this round was genuinely hard. I went through every submission. Pulled repos. Read identity files. Compared rules.md sections. Every entry did real work. A lot of you shipped something I would happily use, sell, or hand a client tomorrow. I can NOT explain to you how proud I am of everyone participating in these, you make this community worth and it and there is SO much potential for the future from just ONE competition let alone future ones. 💼 That part matters more than the prize. The $325 covers a year of Premium and that's great but... The portfolio piece is the real value here. A public repo of a working folder-based AI specialist with a clean README and receipts is a resume line that hiring managers can clone and test cold in five minutes. It is also something you can charge for. If you built a specialist that solves a real problem in a real domain, you already have most of what you need to license it to a peer in your industry, sell it as a service, or package it as a Done-with-You engagement. A few quick notes on that, because most of you did not realize what you actually built and I want to Highlight a few of you: 💸 @Nicolas Patron Uriburu USD Routing Coach AR could be sold to every Argentine indie consultor I know. Same playbook works for any country with FX restrictions. Subscription service, recalibrated annually, audit-pack included. It is a product. 🔗 https://github.com/Nicopatron/usd-routing-coach-ar 🔧 @Jannetje van Leeuwen RAMS specialist is a service business in waiting. Irish signage contractors will pay for this. Same model works for any trade with a regulatory documentation burden. Plumbing, electrical, fit-out, demolition. Each one needs its own folder. 🔗 https://github.com/JannetjeIQ/rams-irish-signage-installer
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
🚀 Vibe Coding is the new Technical Debt. Meet SDD.
If you want to drop this in the Skool community and actually get the attention of the high-level engineers, you need to lead with a pattern interrupt. These guys see "How to prompt" posts all day—you need to tell them why their current workflow is about to hit a ceiling. Here is the exact post I would write for you: Headline: Vibe Coding is the new "Technical Debt." It’s time to talk about SDD. We’ve all seen the magic. You vibe with Claude or Cursor, you prompt your way into a working MVP in three hours, and it feels like we’ve conquered the world. But there’s a wall coming for all of us. Once your project hits 5,000+ lines of code or requires complex state management, "vibing" starts to fail. The AI begins to loop, it hallucinations your file structure, and you spend more time "fixing the fix" than building features. The elite 1% of AI Engineers are moving toward Spec-Driven Development (SDD). The SDD Framework (How the Pros are building now): Instead of jumping straight to the prompt, you insert a "Contract Phase" using two specific files in your root directory: 1. spec.md: The "Source of Truth." This isn't just a prompt; it’s a rigorous definition of every user journey and data model. 2. plan.md: The "Execution Guardrails." This tells the AI exactly how to implement the spec, defining the file structure and API contracts before it writes a single const. Why this is your new "Moat": In a world where everyone can "vibe code," the code itself is a commodity. Your value as an AI Engineer in 2026 isn't your ability to prompt—it’s your ability to Architect. • Determinism: SDD stops the AI from guessing. • Context Management: By referencing a central spec, you keep the "God Object" in the AI's head consistent. • Scale: This is how you move from "cool demo" to "enterprise-grade SaaS." Stop prompting. Start Architecting. Check out this InfoWorld breakdown on why this shift is happening: https://www.infoworld.com/article/4166817/vibe-coding-or-spec-driven-development-how-to-choose.html
From messy to branded profile grid
With very little experience a week ago, I created a project outline to brand out the cover images on Instagram profile grid. In less than 30 min, after going through the foundations i had it completed. Claude code executes with just two words and can make as many cover on demand as i wish and output them neatly as PNG files in a folder. Jake - super thanks! I learned so much in less than a week 🙏🙏🙏🙏 See before and after :)
From messy to branded profile grid
1-30 of 1,108
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by