User
Write something
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
🏆 HOW COMPETITIONS WORK FROM NOW ON 🏆
Quick update on the competition schedule so everyone knows what to expect. 📅 NEW CADENCE: TWICE A MONTH We're dropping comps on the 15th and the 30th of every month. Two chances to compete, every month, on a set schedule you can plan around. ✍️ WHY THIS SCHEDULE Spacing them out this way means we can give tailored feedback on every single submission. Not just the winners. Everyone who enters gets notes on what worked, where it's weak, and what to do next. 🎁 WHAT WINNERS GET Along with the prize, every winner gets a 15-minute one-on-one with Jake. Use it to talk through your build, ask questions, or bring whatever else is on your mind. Two comps a month. Feedback on every entry. Direct time with Jake for the winners. Mark your calendar for the 15th and let's get to work!
Pinned
🎆 GOOD NEWS: THE SALE STAYS OPEN. HAPPY 4TH 🎆
We're holding the last sale through the holiday weekend so nobody misses it. 🎉 Premium: $27 → $14/mo 🎉 VIP: $97 → $67/mo This is the cheapest it will ever be. Once it closes, the price is gone for good. ⏰ New deadline: July 5th, 10:00 AM EST. This is the last extension. If you've been on the fence, sign up now. You lock this rate in and keep it every month going forward. 🖥️ ONE MORE REASON TO JOIN The week of July 5th we're dropping the software we've been building for this community. It goes out for beta testing first, and only Premium and VIP members get access. Sign up before the sale closes and you're in from day one.
I run four phases before any AI builds anything.
Most "AI workflows" are one phase: type a prompt, hope. Mine has four. The build doesn't start until phase four. By then the AI is barely making decisions. It's executing a contract. Phase one: Brainstorm Open conversation. No structure, no acceptance criteria yet, no scope. I yap. Claude compresses what I yap into a `.md` file in real time. We argue. We rule things out. We name the actual outcome I'm chasing, not the thing I thought I wanted when I started talking. The output of phase one is one sentence: **what done looks like.** CRUSH started as "I want a video plugin that feels analogue." Two hours of brainstorm later the doc said: "14 Metal fragment shaders, a 6-slot effect chain, three global controls (DECIMATE, SPAZ, CHILL), real-time on Apple Silicon, drag-and-drop in DaVinci Resolve." That's the outcome that got dispatched. Phase two: Implementation plan Now I take the outcome and ask Claude to architect it. Files, dependencies, the order things get built in, the places it's likely to fall over. This is still in the main session. Still advisor seat. Zero code written. The plan for CRUSH was a 6-stage build pipeline. Format design, build-time generator, plugin core, 2D shaders, splat engine, AE port. Fourteen Metal fragment shaders authored as `.crush` JSON files. A Python codegen that writes the entire C++ OFX boilerplate at compile time so adding a new effect later is JSON plus a shader function and nothing else. Every stage had acceptance criteria, file scope, and risks named upfront. By the time it was done, the plan was a single markdown artefact a fresh worker could execute against without ever talking to me. That's the goal. The plan is the spec. The spec is the thing. The plan also names risks before any worker meets them. It says: "Metal kernel buffer names must match this exact contract or DaVinci silently rejects the bundle." It says: "Real-time on Apple Silicon at 4K is the gate. If a shader drops frames during scrub, it doesn't ship."
🏁 Foundations 1.3 Check-In
You learned the framework. Now try it on something you're actually working on. Vote below, then drop your prompt structure in the comments. Not the output. The structure. Show us how you set it up.
Poll
1341 members have voted
1-30 of 2,248
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