"The haters, the doubters are all drinking champagne in the top deck of the Titanic… and we are the iceberg." — Casey Neistat A couple of days ago I rediscovered one of my favorite YouTube videos, posted 9 years ago by Casey Neistat. The premise is simple: everyone will tell you what you can't do. In life, in business, in relationships. In our case, with AI. F*&% that. When I joined this community a month ago, I didn't know what a markdown file was. Couldn't build a workspace or a system. Had no idea what "IDE" stood for, let alone how to build and deploy skills in Claude. That being said, I did the thing anyway. And now I'm building and solving things in ways I never imagined. If you're new: welcome. Do what you can't. If you've been here a while: keep doing what you can't. This is one of the best communities on the internet. Grateful to be in it.

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.