Built AI versions of 15 of my favorite creators over the last 3 months. Mostly for myself. Yesterday someone asked me how. Today a few more people did. So here's the entire blueprint, free. Pick any YouTube channel. Run Claude Code. Paste one message. Wait 30 minutes. You now have an AI tutor that's read every video on that channel and can answer questions like the creator would. Hormozi-bot for pricing. VanClief-bot for whatever you've been meaning to ask Jake at 2am(Spoiler Alert: this happens a LOT). Your favorite teacher, on tap. Repo: https://github.com/aaronb458/youtube-tutor-template Free version runs on your laptop. Paid version (~$5-10/mo, with $200 in free Deepgram credits to start) lives in the cloud and plugs into Claude.ai as a permanent tool. Both versions are walked through end-to-end by Claude itself — you don't need to know what an API key is, what a database is, or what "deploy" means. You click links. You paste things back. That's it. Posting it here because @Jake Van Clief's content rewired how I think about creative + business + software being one unified system. The only way I know how to repay that is to make sure people in this community can mainline it the same way. Try it. Break it. Tell me what's confusing. I'll fix it.

Bottom line: Two hours. Jake's frameworks went from a folder to live tools running in my workspace. Most community content has a 48-hour half-life. You read it, save it, and it ends up somewhere it influences nothing. The content is fine. The structure is the problem. Here's what I did: --Organized the vault: Cleaned up 30+ scattered files, classified by type, split into five sections. A file you can't find in 15 seconds doesn't exist. --Built an auto-ingestion pipeline: Scheduled task runs nightly. Drop anything new into _Inbox, it classifies and routes itself. New content stays in its lane. --Converted three frameworks into live skills: - Council of 5 — runs on command. Five advisor perspectives on any decision, simultaneously. - 60/30/10 Triage Rule — installed into workspace operating rules. Applies to every task without prompting. - Discovery Call SOP — no longer a document you read mid-call. Phases through pre-call, live support, and debrief automatically. --Audited workspace documentation: Cut 30-40% from routing and context files. Tighter files, faster responses. Before: Jake's frameworks lived in a folder. After: three of them are running. The best part is that it compared it against what my current business needs are and filtered out resources that weren't relevant to me (yet). For example @Curtis Hays full agency or @Roc Lee and his awesome conference talk engine. If you want to replicate it, I've attached a step-by-step guide with the exact prompts I used across all five sessions. Thank you ALL for your inspiration and to @Jake Van Clief for building this incredible community.

Practicing building in public and wanted to share what I've built with help from my other writing brainstorming thread from @Deacon Wardlow and @Siv Darmalingum @E G and @David Trammel Using some of their ideas I did research on the writers and topics they suggested using Notebook LM. I synthesized that research into digestible artifacts for claude to extract themes and guidelines for developing conference talks. I then described to Claude the workflow I wanted to build, can share that prompt if people are interested. And then I also used the workspace-builder as a model for the scaffolding for the conference-talk-engine and my own workspace as models for schema in the Claude and Context mds. The output of all of this was a spec document to build the workspace. I incorporated guidelines to use SOLID principles for coding to allow a built workspace to be extended and improved upon over time without having to rebuild the whole workspace, this is because I think it's better to build a prototype fast and then iterate rather than be 100% perfect. You want to spend time to make sure that the spec doesn't produce errors, but some things will only show up with actual use cases. I then researched existing skills relevant to my use case and came up with 2: conference-talk-builder and giving-presentations. I asked claude to evaluate my research and the existing skills to see what gaps could be improved in the existing skill. I then asked it to write the spec After first draft of the spec I ran a reader-test which is a custom skill derived from @Ari Evergreen 's 6 phase workflow. A rough breakdown would be: 1) research data inputs and relevant skills, compile any useful context relevant to your workflow; 2) analyze inputs with claude; 3) describe your ideal workflow and any models you want to emulate, make sure to mention you are building a spec first; 4) review plan for spec; 5) draft the spec using claude; 6) reader-test to qa the spec.

I am known to take Claude outputs and put them into ChatGPT for blind-spot checks. Today I decided to create a "council of 5" skill that runs any question, problem, solution, document, etc., through 5 distinct personalities, with 3 rounds of discussion, then a consensus. 1. The professor: peer-reviewed/cited sources only 2. The teacher: logical, wonders, "is this the right question to be asking" 3. The founder: can this be done, and what is the fastest way 4. The outside: zero context, thinks outside of the box 5. The contrarian: hunts for the fatal flaw in everything. Sharing the skill here if it could help anyone.

It’s not: “we cleaned files” It’s: “we built a system that keeps itself clean.” The first month I was just trying to get my head around the Foundation, Implementation and understand what is happening. Foundation already gave me a Content Provider style architecture, along with the animation and website builder, i intuitively and with both ChatGPT and Claude I started by implementing Jake's structure. I watched YouTube videos as well that gave me other insights (and validated that Jake's course is the only place that i see that talks about ICM and Architecture and such). Either way, I signed up for premium yesterday, and found that there was much more to complement the Foundation. As Jake suggested, I slowly took each on of the Vault items, and explored with Claude - how is our architecture compared to GitHub repos (which I tapped into some of the members GitHub repos and made Claude check itself against those insights - super thank you Community!!). It pointed out a few times that our architecture is more mature, though it always found 1 or 2 items that could improve its flow. We had a glitch this morning when I prompted the execution of today's schedule with all the items to post, create and monitor, which the Orchestrator and Operator (me) had to dissect what it did and ensure it won't follow that course again, and whether such a flow is efficient both Token costs and Workflow. It found ways to optimize - extracted what it found useful from the Vault, informed that skills that mention in Vault are skills we already captured (among others). My very first project with Jake - text to video animation has been improving on its own outside my Brand Sandbox. And as I closed my Claude after uploading the content it had structured neatly for me in an HTML file with EVERYTHING that i needed for the content posting, I had it summarize its work - which I hope this help if you read this far (thank you for reading my stuff:)) - Three-day architecture delta (Apr 30 → May 3)