🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 📋 THE CHALLENGE You are the client this week. No fictional Marcus. No fictional Sarah. No fictional Devon. Pick a real problem in your own life or work. Build the folder-based specialist you wish you had. This is the capstone of Month 2. The challenge flips. Instead of building for someone else, you write your own brief and solve it for yourself. ---- 🎯 THE TWIST The hard part isn't building. The hard part is scoping. Picking the right problem is harder than solving the wrong one. Most people pick problems that are too small or too vague. The skill this week is treating yourself like a real client. Be specific about what's broken. Be specific about what you need. Don't pick "I want to be more productive." Pick "I waste two hours every Sunday night writing the same kind of LinkedIn carousel posts and I need a folder that handles 80% of the draft work so I can focus on the hook and the visuals." That's a real brief. Specific problem. Specific scope. Specific desired output. ---- 🗂️ TWO DELIVERABLES THIS WEEK This is the only week with two pieces: 1️⃣ Your own client brief. 250 words or less. Describe the problem you're solving for yourself. Treat yourself like a real client. What's broken? What have you already tried? What do you need? 2️⃣ The folder system that solves it. Same structure as every week: - 📄 identity.md - 📐 rules.md - 💬 examples.md - 📚 reference/ - 📖 README.md Your brief lives at the top of the repo as brief.md so judges can read it before they look at the folder. ---- 🔥 THE ANGLE THIS WEEK Anyone can follow a brief. Writing your own, then solving it, then shipping it as a usable folder is a portfolio piece that demonstrates judgment, not just execution. This is the skill that separates "AI hobbyist" from "AI builder." Anyone can prompt their way through a problem someone else handed them. Scoping a problem, designing the solution, and shipping it as a system is what real work looks like. 💪

I’ve been in this group for 3 months now. I have definitely learned more in this time than I did in my entire life or at any point in my education, and that’s no exaggeration. Before I found this group, I knew nothing about AI; the whole hype train around it just put me off wanting to learn more. Too much “oh, it’s the worst thing ever” and too much “oh, this is the greatest thing ever” — so much whiplash from competing opinions is hard to get your head around. If you’ve been in this group as long as I have, it’s probably crystal clear that this is exactly where you want to be in this age of AI. The knowledge here outranks everything else, hands down. Trust me, I’ve been researching this non-stop, and I just wanted to share a summarised think piece from a recent chat I had with my system. It is AI-generated; I’m a delivery driver, not a writer 😅 — part of the beauty of AI, right. Draft post: I’ve been thinking about the difference between agents, skills, workflows, and systems. A lot of people are building “AI operating systems” by making loads of fixed agents: Research agent. Marketing agent. Coding agent. Sales agent. Browser agent. That works to a point, but I think it can become the wrong frame. Because the agent is not the main thing. The real thing is the structure underneath it. An agent is just the worker shape for the task. A skill is not magic. It is not some special power the AI secretly understands. A skill is really a reusable packet of instructions, files, examples, rules, and checks that tells the agent how to do one type of work properly. A workflow is the chain that says what happens first, second, third, and what must pass before the job is done. A system is the bigger operating layer that decides: What is the mission? What context matters? Which skills are needed? Which worker shape should be created? Which files are the source of truth? What gets checked? What gets rejected? What loops again? What gets saved? That’s the difference.

That's the leap most people never take. Roughly 90% of our members are still on the other side: scrolling, saving, getting value, never saying a word. Not a knock. Just the math. Lurking isn't failure. It's the default. But you showed up. And that shift compounds fast. The classroom teaches you the tools. The community teaches you how to think with them. When you participate, you get compression — months of grinding folded into a thread someone else already broke so you don't have to. Less friction. Faster outcomes. Personal growth and business growth in the same lane. You don't need a hot take. You need a real question. Give before you extract. Your lurker era wasn't wasted — you were loading context. Welcome to Level 2. A few of you just made the jump, and I want to call it out: • @Vamsi Acharya • @Stacey Lubowa • @Martin Brion • @Mark Benjamin • @Keith Langskov • @Patti Wilcox • @Novus Vella • @Tony Rhodes @Cain Gray If you're still lurking — go check out what they're posting. Real builds. Real questions. No fluff. That's the energy we want in here. And if I missed you — my bad. Drop your name below. We'll get you in the next round. The reward for showing up isn't points. It's speed. You stop duct-taping alone. You stop renting confusion. Your stack starts to click because other people's scars are now in your context. What finally made you break the ice? ───

hi there everyone 😊 a question: i am working on my ICM setup. comes with a certain amount of cleaning up. what are you doing with your /skills? since ICM is supposed to make your agents independent of a certain AI, I would think that my claude /skills are supposed to be history and what they are doing is now job of the ICM, so......? Edit: 5 minutes later 😀 the modern ICM /skill I S as close to the workspace as possible. true / false?