💰 $500 CASH 💰 Win this and you've covered a year of Premium with $175 left over. 📋 THE CHALLENGE Build a folder-based AI coach for a specific domain. You pick the domain. This week's deliverable is one coach folder that someone could drop into a Claude project and use as their personal coach for whatever you've built it for. 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎤 Public speaking coach for new managers giving their first big presentations - 💼 Salary negotiation coach for tech workers at Series A startups - 📞 Cold call coach for first-year SDRs in B2B software - 🎯 Interview prep coach for product manager roles - ✍️ Writing coach for one specific genre (sci-fi short stories, college essays, op-eds) - 🏋️ Fitness form coach for one movement (squat, deadlift, golf swing) - 🌍 Language learning coach for one use case (medical Spanish, business Mandarin) - ♟️ Chess coach for one specific opening or endgame pattern - ⚽ Youth athletics coach for one sport and age group The more specific, the better. "Life coach" is too broad. "Salary negotiation coach for tech workers at Series A startups" is right. 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning the foundation of interpretable context methodology. Folders as architecture. Each file does one job well. Your coach is a folder with five things: - 📄 identity.md (who the coach is) - 📐 rules.md (how they coach) - 💬 examples.md (what good looks like) - 📚 reference/ (frameworks, drills, source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the coach. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK A coach is NOT a knowledge base. A coach gives feedback. Pushes back. Asks better questions. Holds people accountable.

"Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time." https://x.com/karpathy/status/2056753169888334312?s=20

Dropped a new one for you all. Mike from Urban Pulse let me share footage from his security audit. He vibe coded his whole platform using my routing architecture, then hired me and my team to read every line before he opened it up to high ticket clients. We took our time over many hours. We found three holes that I share here. A Google Maps API key that had already been flagged and locked down by Google. A second cryptographic auth layer the AI built on top of Supabase, which already handles all of this for you. A JWT verification step that never checked the issuer, meaning any valid Supabase token from any project on the internet would have passed. This is what real building and shipping looks like in the AI world. Mike built something that used to take a year and a couple hundred grand. He did it solo. Then he paid engineers to audit it before any customer touched it. Copy his move. If you are vibe coding anything you plan to put in front of paying clients, watch this one.

This is a build session, not a lecture. Plan mode. Sub-agents. Watching Claude fetch repos, study your workspace, and sometimes make better decisions than what you asked for. The point isn't to follow along exactly. It's to see how a real build actually happens. What stood out?

You just saw how the folder structure adapts to different use cases. Vote below, then drop your customized setup in the comments. What did you name your workspaces and why?