User
Write something
New Member Onboarding. is happening in 5 hours
Pinned
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
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. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 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 The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 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.
Pinned
🌵 ANNOUNCEMENT: THE LEGENDS CLASSROOM IS OPEN 🌵
Gather round, Clief Notes crew — we’re opening The Legends: a classroom on the Frontier built around two gunslingers who deliver real systems, not hype. Each legend has a dedicated folder packed with signature builds, frameworks, and battle-tested wisdom. Start where the dust is thickest for you. 📐 Bas Rosario – The Wise Architect’s Library Master planner and blueprint boss. Bas designs for deep understanding and human–AI collaboration so you stay in control — frameworks, systems thinking, responsible AI, and work that still feels human. 👷‍♂️ Don Roy – The Master Builder’s Forge Hammer in hand, fire in the forge. Don turns ideas into working tools: automation, quality control, content systems, Remotion + AI builds, and anti-slop standards that keep what you ship durable. These two are the heartbeat of this classroom — grinding, growing, and lifting the whole crew. Your move: Pick a folder. Open it. Start forging. https://www.skool.com/cliefnotes/classroom/b5143824?md=61c684c877384eefbd11c804f83aac05 Who are you riding with first — Architect or Builder? Drop a 🤠 below and go make something that lasts.
🌵 ANNOUNCEMENT: THE LEGENDS CLASSROOM IS OPEN 🌵
Did I find my AI voice - I think so
Hi All... Quick geek out moment... (Yes this is a thing that I am fully embracing and each LinkedIn post is now exactly about that.. Geeking out about the things I learn here - not just from Jake, but from everyone - if I mention your work (trust I will tag you - ask Don or Jake -shame I think he gets spammed with LinkedIn notifications saying the weird one in South Africa has tagged you - again) ##Quick note if you think I might tag you or reference your work and you do not want to be mentioned or named - just send me a dm and I won't mention you## Why I am posting about LinkedIn - I always thought I had to be very "LinkedIn decorum - in my head think monocle and a cup of tea with a top hat for good measure" and I dropped it and started just geeking out... And funny enough people are noticing. In such a way that a CEO of an Educational company has reached out to me, he wants to introduce me to their COO as he thinks their might be opportunities in teaching AI to others. He loves what I am doing with AI. It is not a set in stone but their might be - and all I really need is a shot - right? Not just that after helping my brother reorganise his system to help with his Masters (yeah I edit and help write Master thesis' for fun - everyone should have a hobby) but he spoke to his supervisor about me - and I will be meeting her in a few hours to talk about doing my PhD (It does not really fit into any of the programs that are available ##apparently: MA Practical Theology turned Afrikaans teacher (with PGCE) turned Mathematics teacher (Certificate in teaching Mathematics FET) turned Robotics/Coding/EdTech teacher and Head of IT department turned, hey I know things about AI now and I have done like Clief Notes videos (and a few not that great others) and Ethics Courses and have read like a ton of research articles and I want to write a thesis on "Host don't hold: The shredder principle" - it does not fit into a specific doctoral degree option...who knew ## But after my brother (he has no idea what I am showing him most of the time but he gets excited too) talked to her - she said she is willing to meet with me to help me figure it out and she might even have a supervisor. #Excitement - even if it does not work out how cool is that I might be one step closer to doing my PhD. Yay (I promise I sound more legit in academic writing)
I've been testing image models since the local SD era. AMA.
Most people met image gen after chat made it mainstream. I met it earlier, on local hardware, with Stable Diffusion, when the job was still: make it run, make it hold, make it fail honestly. That history is not a flex. It is a testing habit. The yardstick When I try a new image model, I do not ask "is it pretty?" I ask: 1. Does a tight inventory hold (counts, props, who is in frame)? 2. Do hands, materials, and grit survive, or does it go plastic? 3. Is the light documentary, or beauty-filter default? 4. Can I lock a still before I trust motion? Pretty without a yardstick is noise. The method (still first) What I run, even on cloud models now: 1. Subject + action first. Not camera brand names. 2. Fill the frame with the work (centre subject, intentional crop). 3. Mechanics checklist (hands on tools, cables, sandbags, real set mess). 4. Light as production light, not influencer key. 5. Materials named (dust, tape, fabric, metal) so the model cannot invent void. 6. One craft lock (film still, grain, matte blacks) plus a hard forbid list. 7. Still first. Motion second. Never use video to fix a weak plate. If the still fails dual judgment, I re-roll or refine on one axis. Wording or seed or a small edit. Not all three at once. Proof attached For this post I ran that same discipline on a brief I care about: Behind the scenes of a film being recorded. Ultra-wide 21:9, centre-framed subject. Still locked, then motion from that plate only. Not decoration. A live test of whether the stack holds a real set. Floor is yours Ask me anything on: 1. Prompting for messy real environments (sets, hands, practicals) 2. Workflows still to motion, local era to cloud era 3. Gen judgment how you know something is good enough to ship I'll batch replies this week. No wrong questions. Specific beats welcome ("how do you kill plastic skin?", "what do you ban by default?"). More of my work: https://pushingsquares.com/ari
I've been testing image models since the local SD era. AMA.
1-30 of 2,735
Clief Notes
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)
Powered by