First post here, so be gentle, lol. I'm having a hard time wrapping my perception about what kind of data you can, or should put into yours for your AI memory. I've been messing around with computers and by extension data manipulation, since the 70s. I have a good understanding of how a relationship database runs. But we're not building that kind of ecosystem(?) are we? We can go bigger. Before I dug deeper, I always picture an LLM like Chatgpt, as having this huge massive brain, which held all of the Internet, and when I asked would wave it's virtual hands to say "Here it is". I know that's incorrect. I'm using AI as a research assistant and junior co-writer. I'm doing a non-fiction book what kind of skills you'll need to make money in the next 20 years. I'm doing a ton of digging for trends and possibilities and...all of you have a good idea of what that means, I'm sure. I went into this thinking it would be more like a Wiki compiled form all my research and conclusions but is that what I want? Seems like there so much more than just a glorified book list. I do want to have a folder style system, with the full transcripts, complete articles, or other important documentation that I need. That's doable too. But recently, I wanted to start at least collecting the base data. If I don't start doing that, I'm just digging my hole deeper. So I laid down a basic schema, and then asked GPT to pull me 5-6 highlights that it thought should go into the database. Once I get the workflow built, I pretty sure I'll try to automate it, so as I research, the AI formats and stores any highlighted data I come across. It pulled those six, then another three from our discussions on the first six, and we were in a side chat at the time, the main chat was on markdown files. We got 10 entries from that. So I had nineteen. I haven't done any more, but when I look at what I have, I get this weird vibe that the majority of them aren't on the book subject, but are more of how the LLM views the way I work? That's a poor description of it, I hope it works.

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.