Hey guys, I'm Matt, an indie designer/developer in LA. I run a solo studio (client work and my own products) and a local security camera business. Besides those I'm usually tinkering with local LLMs, 3D printing, or robotics. I randomly came across one of Jake's youtube videos not too long ago and was about to close the tab expecting the usual guru-slop content. But when I saw his desktop wallpaper, I knew I had to watch all his videos. (If you're into DBZ we're already friends) So now I'm here and glad I joined! I already learned a lot but I'm trying to figure out how to organize my folders for 2 businesses and a bunch of side projects. Has anyone else here struggled with that? Would appreciate some help. Anyway, I look forward to learning, building, and connecting with you guys. Hit me up if you're a fellow designer, developer, DBZ fan, or if we share any interests like 3d printing, etc.

I've been super busy with my head down getting a lot of work done, and still pretty busy but I had to block a little bit of time to vent. So yeah. Claude and I are done. I had to apologize to my content manager's kid because I was cussing out Claude on a work call and I didn't know he was within hearing distance. Monday, during our Sales & Marketing meeting with Amanda and Luis, we were trying to fix a LinkedIn post we'd already gone through a few times. I asked Claude to start fresh and leave the old draft out of its context. It went and read the old draft. Then it tried to change our root instructions. Opus 5 has been a trainwreck since it was released, and even with Opus 5.5, I was still having to check whether it had followed the process we'd already put in the files. We eventually got a better post. I'll give it that one. The storytelling pulled me in. But I hadn't seen it run the hook check, the step we'd told it to use to find the strongest opening. "did you run it through hooks to optimize the opening?" "No, I skipped it. Running it now." No explanation, no apology, and to add insult to injury, the stupid AI thought for 0 seconds... I've attached the screenshot. You can admire the moment my remaining patience packed its little suitcase. "I hate you so much, Claude." I said that out loud. On camera. While leading a meeting. Amanda's kid was on the couch, so I followed my contribution to workplace professionalism with an apology. Claude does overdramatic prose so well that I'd had to throttle it back. Apparently, after all that exposure, I'd started supplying the drama myself. Somebody put parental controls on the boss. ------------------------------------ I'd already moved. My team hadn't. ------------------------------------ I'd been doing almost all my own work in ChatGPT/Codex for about two weeks. Better experience, better results, for me. Meanwhile, the rest of my team was still using Claude. I told them it was unfair to leave them working through the same stuff I'd gotten sick and tired of. Amanda had a ChatGPT seat before the call ended.

📣 Update (10/8/26): Comp 14 Rules Added Current Challenge: Competition 14 The Challenge 💪 - Build a specialist of your choosing, run a test, AND run a control to compare it against. Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-14-the-control?p=378868a2 Good luck everyone! --- What this thread is: I’ve seen a number of people either not know competitions are going on or know how to find them so here is a quick single source thread where you can get to them all. I’ll keep this updated as new challenges are released. See the current challenge as well as all past challenges below! Format for community challenges: https://www.skool.com/cliefnotes/how-competitions-work-from-now-on?p=84912d60 Weekly leaderboard competition: Alongside the biweekly challenges, there is a weekly leaderboard challenge where the member at the top of the 7 day rolling leaderboard wins a free upgrade to their membership. This winner is announced on Mondays typically. @Joshua Hubbard has gone another step further and created a thread linking to all competition entries. Link here: https://www.skool.com/cliefnotes/the-competition-archive-every-entry-every-week-every-link?p=bd752987 --- Past Challenges Competition 1 The Challenge 💪 - Build a brand voice document for a pet grooming business Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/first-ever-weekly-competition-is-live?p=90f50bf9 Results🏆 - https://www.skool.com/cliefnotes/weekly-comp-1-winner-ian-barriopedro?p=0501b57e Competition 2 The Challenge 💪 - Build an artifact of a financial advisor client intake system

This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post.

This is the website I created for them — pikolhaus.com. Small start, but officially my first real client project. More to come.