Before I get to the who and why, I want to say this plainly. Picking a winner this round was genuinely hard. I went through every submission. Pulled repos. Read identity files. Compared rules.md sections. Every entry did real work. A lot of you shipped something I would happily use, sell, or hand a client tomorrow. I can NOT explain to you how proud I am of everyone participating in these, you make this community worth and it and there is SO much potential for the future from just ONE competition let alone future ones. 💼 That part matters more than the prize. The $325 covers a year of Premium and that's great but... The portfolio piece is the real value here. A public repo of a working folder-based AI specialist with a clean README and receipts is a resume line that hiring managers can clone and test cold in five minutes. It is also something you can charge for. If you built a specialist that solves a real problem in a real domain, you already have most of what you need to license it to a peer in your industry, sell it as a service, or package it as a Done-with-You engagement. A few quick notes on that, because most of you did not realize what you actually built and I want to Highlight a few of you: 💸 @Nicolas Patron Uriburu USD Routing Coach AR could be sold to every Argentine indie consultor I know. Same playbook works for any country with FX restrictions. Subscription service, recalibrated annually, audit-pack included. It is a product. 🔗 https://github.com/Nicopatron/usd-routing-coach-ar 🔧 @Jannetje van Leeuwen RAMS specialist is a service business in waiting. Irish signage contractors will pay for this. Same model works for any trade with a regulatory documentation burden. Plumbing, electrical, fit-out, demolition. Each one needs its own folder. 🔗 https://github.com/JannetjeIQ/rams-irish-signage-installer

💰 $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.

First, thank you to everyone. Three weeks ago this community had 1,600 people. Today we're at 11,700. That kind of growth only happens when people show up, engage, and tell others about what we're building here. So before I get into the details: thank you for being here. Thank you for the questions in the comments, the builds you're sharing, the conversations in Discord. This community is what it is because of who's in it. Now, the news. Premium is going from $7 to $27. VIP is going from $49 to $97. Free stays free and it always will! Ready to join? Head to Classrooms and click "The Vault" for Premium or "The Drawing Room" for VIP. It'll walk you through the rest. Why the price is going up: The content scales. The courses, the templates, the frameworks. All of that can reach 10,000 people as easily as 100. What doesn't scale is Jake. The live sessions, the critique queue, the bespoke builds. That's Jakes time, and there's only so much of it. The price increase reflects that. Grandfathering If you sign up for Premium or VIP before April 4th at 11:45 pm EST, you lock in the current price. $7 for Premium. $49 for VIP. That rate stays yours as long as you stay subscribed. This applies to new signups and upgrades. If you're already in a paid tier, you're already locked in. April 4th, new prices take effect for everyone who joins after. The free tier is still free and always will be!! And here's the thing: the paid tiers are what keep the free tier free. When Premium and VIP members invest in direct access, it means Jakes doesn't have to paywall the fundamentals. The Foundation can stay open. The courses can stay free. The community keeps growing without anyone getting locked out of the basics. Everything in The Foundation stays open. The courses, the community, the conversation. The free tier remains a full learning environment with more content than most paid communities offer. We'll also keep sending out community questionnaires like the one I sent last week. When Jake goes live to talk through the results, those recordings get posted for everyone. Expect these every month or two.

Is anybody using AI to generate LinkedIn content? If so, are you using the md file system thaught by Jake or something else?

Open sourced a memory management plugin for Claude Code (and Cowork) a little while back. @David Vogel asked for the architectural specifics, so I'm happy to oblige. Some interesting observations and findings in it, but I could really use a researcher's endorsement for publication on arxiv.org under CS.AI. Referrals are deeply appreciated. https://nominex.org/research/what-we-found-building-poor-mans-multi-agent-memory.html Full disclosure: while I said "multi-agent" the reality of it is that the orchestration layer predominantly runs as a single agent roleplaying different agents depending on the folder it's running in. This is the main lesson @Jake Van Clief means when he speaks of folders. Being the over-engineer that I am, sometimes I am tempted to run tasks with multiple agents running in the background. PMM makes it quite context-window efficient (so I don't burn as many tokens or run into message limits on Claude Code).