Howdy friends :) What path have you taken after starting here? 1. Thrown Jake's folder architecture into claude + your project needs to get something fast 2. Used Jake's folder architecture as a template, editing it line by line to plan, think, and produce what you need I'm starting to build a folder architecture with the aim of being able generate brand assets for my company to use across digital, social, and print. In doing so, I'm finding that I have to THINK! 😂 I also sense that this slow trudge is helping connect the dots from the classroom lectures. It feels slow, like hiking through a bog, but I believe it'll solidify some lessons. What do you all think about moving slow to go fast (with AI)?

Debating whether to share a project for initial feedback, it's a math game called MathMines, currently on Lovable. Wondering: -How do you know when a version 1 project you're working on is ready/safe to be shared in a community like this one? -What are your security check boxes? -Are there any best practices or protocols one should follow when first launching a project? Still trying to figure out how i could implement Jake's folder system for Version 2, gonna jump into Claude code for that one.

Context: I want to pitch a few talks to conferences in my field (game audio), and its not something I do regularly so I don't have established workflow for it. I do write linkedin posts and prep for my DND sessions, but that output is significantly different than a 30m to 1hr talk. I've been doing one approach, which I'll outline below, but I'm wondering if others have done this and have a more efficient way of getting to a final result, the below took me 2 sessions both a few hours each, and I'd love to compress that. Wondering about other approaches or resources to help create a better framework. Current process (captured in a skill after finishing last submission): 1. Claude asks : "What could you talk about from memory right now, without looking anything up?" and "What do you know how to do, or think about, that most people in your field don't?" (this takes a long time) 2. feed it which conference, deadline, and format the talk submission is 3. Claude researches past accepted talks for fit and content 4. We lock in thesis, pillars, and target audience (this takes the longest) 5. we do a draft in this order: Description, takeaway, outline 6. Pre-submission review (this part is easy with humanizer and the conference form submission) Wondering if there are places I could improve? And how would others approach this?

Twenty-four days ago I posted about Jake's folder system video. This is what happened next. Same foundation — markdown files, orchestration prompts, clear roles. I just kept building. Fifteen named specialists. Each one with a soul file, guardrails, and a playbook. Duke orchestrates. Cash writes. Trace pulls the data. Hank runs the financials. Clint handles the MCP integrations. Behind each one is either a human counterpart doing the real work alongside them — or a role I can't afford to hire yet. Katie who's been with me for 18 years, now has her own orchestrator running the same system. Twenty-seven client folders. Twelve live MCP integrations. One shared repo. The folder system isn't replacing my agency. It becoming my agency. Jake gave me the unlock. This is how it's going.

Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.