Write something
Pinned
👑
⭐
3d •
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 •
🏆 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
4d •
🎆 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.
1d •
Central map or per-project maps?
Small test from the last couple days: I started treating context as two layers instead of one pile. Raw evidence stays raw: notes, screenshots, logs, exports, messy captures. The operating context is rewritten separately: short index, current state, rules, and next actions the agent can actually load. That made the workspace easier to reuse because the agent is not asked to carry the entire history every time. Question for people running multiple workspaces: do you keep one central map that routes everything, or a small map inside each active project? I can see both working, but I am leaning toward per-project maps with a tiny global index.
2h •
Before you build an agent, find the bottleneck.
People jump straight to “what agent should I build?” That creates unnecessary Agent sprawl. You get personas with no clear responsibility, prompts pretending to be operators, and Agents acting befre the workflow is even proven. Start with the bottleneck. Ask: "Where does work keep getting stuck?" or "What responsibility keeps repeating?" or "What output would prove the role is useful?" Then keep it low-control first: checklist, workflow, prompt, human-assisted role. Only turn it into a named agent when it has a trigger, inputs, boundaries, outputs, escalation, and review. here is a simple progression framework: - Name the responsibility first. - Prove the workflow second. - Create the agent last. Edit: attached methodology from Growth OS
1-30 of 2,262
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
🔥
+1744
2
🔥
+1639
3
+1414
4
+907
5
+620
Powered by