💰 $325 CASH PRIZE 💰 That's a full year of Premium. Win this and your membership pays for itself. 📋 THE CHALLENGE You just got hired again. Different client this time. Meet Sarah, a freelance copywriter who's drowning in context-switching. 📎 Download the full client brief attached to this post. Short version: She works with three types of clients (SaaS founders, ecommerce brands, local service businesses) and starts from scratch every project. She doesn't need another tool. She needs a system. Your job is to build her a folder-based AI specialist she can drop into any Claude project. The folder IS the deliverable. 🗂️ THIS WEEK YOU LEARN ICM Up until now, comps have been "build a thing." This week you utilize the methodology taught throughout the community. 🧠 Folders as architecture. That's it. That's the whole concept this week. Your specialist is a folder with five things: - 📄 identity.md (who they are) - 📐 rules.md (how they respond) - 💬 examples.md (what good looks like) - 📚 reference/ (source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the specialist. Reusable. Shareable. Portable. 🎯 PICK YOUR SPECIALIST Don't pick copywriting. That's Sarah's example. Pick something YOU would actually use. A few sparks to get you thinking: - A salary negotiation coach - A meal planner that knows your dietary restrictions - A code reviewer for your stack - A real estate market analyst for your city - A technical recruiter screener - A grant writer for nonprofits in your space The more specific, the better. "Marketing expert" is not a specialist. "B2B email expert for enterprise SaaS targeting CFOs" is. 💼 WHY THIS ONE LANDS ON YOUR RESUME Real talk. Winning a comp in a Skool community doesn't get you a job by itself. But shipping a working folder-based AI specialist with a clean README and a public repo? That's a portfolio piece.

If any of you have his twitter/linked in, totally comment and tell him to respond to my email. Want him to come chat with all of us and I think he would be happy to just need him to get eyes on, as someone who gets thousands of emails a day I would not be surprised if he never sees it even if it is valuable.

📊 You've probably seen this chart floating around LinkedIn and Twitter Each dot is 3.2 million people. ⬜ Grey is the 84% of humans who have never used AI 🟩 Green is the 16% who have used a free chatbot 🟨 Yellow is the 0.3% who pay for one 🟥 Red is the tiny sliver who use AI coding tools Most of the people sharing it have not actually said what it means. So here it is. 🔁 We live inside an algorithm. Mine shows me AI all day. Yours probably does too. Every reel, every post, every podcast clip, every ad. The feed makes it feel like the whole world has moved on without you and you are sprinting to keep up. Inside Clief Notes that feeling gets louder. You log in and see people building agents, shipping side projects, automating their inbox, talking about Claude Code and MCP servers like it is normal. In this room, it is. Step outside and almost nobody is doing any of it. 6.8 billion people have never opened a chatbot. Plenty of the ones who did opened it once, asked it something dumb, got a dumb answer, and decided the whole thing sucked. They are not coming back this year. Maybe not next year either. 🪖 When I was in the Marine Corps I never felt like I was doing anything special. I was surrounded by other Marines. Everyone around me could do what I could do. The standard was the standard. It was not until I left and stood next to people who had never served that I understood. The thing I thought was ordinary was rare. I just could not see it because I was inside it. That is what is happening to you in here. If you feel behind in this community, that is the right feeling to have. It means you are standing next to the people pushing the edge. Step outside this room and the thing you are calling behind is so far ahead of where most of the world is sitting that they cannot see you from where they are. And do not forget. The thing you built last week, the workflow you set up this morning, the conversation you just had with Claude. A version of you from two years ago would have paid good money to do any of it.

14 likes. Most in the comments. Community voted, and @Ian Barriopedro took it. $200 cash. Yours. Check out his entry here: https://iatoba72.github.io/ruffcuts/ He didn't just write a brand voice doc. He built a site for it. Structured the whole thing so anyone Dana hands it to can actually use it. That's the bar. For everyone who entered, real talk: the quality across the board was strong. This was a tight vote. If you didn't win this round, you've got another shot coming. What's next: Comp #2 drops soon. Heads up though, we said it in the rules and we meant it. The challenges get harder from here. More creative. More technical. This first one was the warmup. If you're a free member watching from the sidelines, this is your sign. Premium and VIP only for comps. $200 cash up for grabs every week or a free lyceum entry!! @Ian Barriopedro , congrats. Dm me so I know where to send the cash. Everyone else, get ready. Next one's coming!!

So in my daily work sometimes I run into brand new code bases that I have zero insights into. And given that I am not a developer by trade, I came up with this prompt and wanted to share it with you all and see what kind of results you got or how we could improve it. This is intended to map out the entire systems in a folder structure that creates permanent context for the agents, let me know your thoughts! I’ve used this structure to keep a 97k+ lines of code projects in check, and seems to work pretty well. Ps not sure why the markdown gets converted to a docx on my iPhone 🤣 .Agents/ └── Technical_Documentation/ ├── README_PROJECT_OVERVIEW.md ├── EXISTING_DATA_MODELS.md ├── API_REFERENCE.md ├── ARCHITECTURE_MAP.md ├── DEPLOYMENT_GUIDE.md ├── ONBOARDING_GUIDE.md └── diagrams/ ├── system-overview.md ├── data-flow.md └── api-flowcharts.md