TL;DR /brofessor is ICM-based skill that helps clean up AI-agent workspaces. It's also a small persona factory: the audit engine stays the same, but you can switch and create personas, and even tune them with a CONFIG.md It checks whether your docs, routing, stages, review gates, and context-loading patterns make sense. It finds bloat, confusion, contradiction, and overbuilt process junk. Then it proposes the smallest safe fix, waits for approval, executes only what you approve, and wraps up with a clear synthesis. It is half workspace auditor, half context janitor, half theatrical menace. Yes, that is three halves. The math is fine. Keep moving. Grab it, run it on a messy workspace, and let it bully your docs into behaving. - Brofessor iight now that that's out of the way, I'm going to explain why this shit actually bangs - actually fuck it imma let him explain this too. ps - this skill was made in 3 prompts, I can show you how I did it if anyone's curious... - yuckyyy Yep — replace the longer **“How It Works”** section with this: ```md ## How It Works Brofessor works because the prompt is built like a layered workspace auditor, not a generic “clean up my docs” request. ### 1. Core Directive: Treat the Workspace Like a Factory The prompt frames the repo as a multi-stage context system: - each stage has inputs - each stage produces outputs - each stage loads only what it needs - stable rules live outside active work - review gates control movement between stages So Brofessor is not asking, “Are these files tidy?” It is asking, “Can agents move through this workspace predictably?” ### 2. Layer Model: Give Every File a Job Brofessor audits through five layers: - **Layer 0:** workspace identity - **Layer 1:** map/orientation - **Layer 2:** routing/context loading - **Layer 3:** stable rules, contracts, criteria - **Layer 4:** active products and outputs This prevents the classic markdown soup problem where `CLAUDE.md`, `CONTEXT.md`, plans, rules, drafts, and review notes all start pretending to be the boss.

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