I sorta figured it out by now, it's 3 months old.

Hey Charlie — I'm setting up the four base-folder workspace from the lesson and hit some confusion about where the .claude subfolders (agents, commands, hooks, output-styles, plugins, skills) are supposed to live. I discovered I actually have two .claude folders: 1. A global one in my home directory (C:\Users\PC\.claude) — this already has agents, commands, hooks, plugins, and skills folders, and it's where all my installed plugins/skills actually live. 2. A project one inside my workspace (.../vibe coding/.claude) — this one is empty. My VS Code explorer only shows the project folder, so I couldn't see any of my installed plugins at first and thought something was broken — turns out they were just in the global folder one level up. My question: When you say to build the .claude/ structure with a you mean the global .claude (applies to every project) or aper-project .claude inside each workspace? And should I be creating those subfolders in both, or just one? Trying to make sure I set up the workspace the way you intend before I start building. Follow-up: Would the goal be to move my global .claude out of the root/home directory and repoint Claude to work from my workspace folder instead — so everything lives in one place I can actually see in my explorer? Or is having the global one separate from the project one actually the intended setup? Thanks!

Hi everyone. We're building a personalized outreach intake system for processing immigration leads, meaning an immigration law firm will hire us, use the system to qualify and screen their leads, and help them sign up cases. We're looking at ways to have a natural-sounding voice. We're currently using Retell that we have with Twilio as the primary phone system, and then behind that we were looking at using Eleven Labs to have more natural-sounding voice than the voice provided by Retell. Currently, the process of this is to have it all synced Go High Level to schedule paid and unpaid appointments for people and do post consult follow up. How have people found more natural-sounding voices with AI so it doesn't sound like AI itself?

PROOF, somethings are not always possible when you’re using only a phone. 😉

JUST GOT MY BOTTLENECK REPORT Took the AI Bottleneck Finder at charlieautomates.com/diagnose and here are my results: STAGE: The Explorer PRIMARY BOTTLENECK: Agents, Skills, Workflows: Too Many Doors, No Key Darren, you named three things in one sentence: agents, skills, and workflows. That's the tell. When someone can list the menu but can't pick a meal, they're not lazy, they're paralyzed by options. You want to learn how to 'create, automate, AND prioritize' all at once, and that's exactly what's keeping you stuck at the starting line. HIGHEST LEVER: Your highest lever right now is picking ONE workflow and building it all the way to done. Not an agent. Not a system. One workflow, one problem, one output. Open Claude Code, describe a task you actually do in client work (even if that's minimal right now), and build something small that works. The shift isn't from operator to owner yet. It's from tinkerer to builder. That first completed thing rewires how you see everything else. QUICK WIN: Open Claude Code right now. Type this prompt: 'I want to build a simple workflow that takes a client intake form response and drafts a follow-up email. Walk me through building this step by step.' Don't skip ahead. Don't Google alternatives. Just build THAT thing. You'll have a working prototype in under 90 minutes and you'll finally know what 'building a workflow' actually feels like instead of just reading about it. What does yours say? Take the quiz: charlieautomates.com/diagnose