VIP members: High Tea is coming up. If you've got something you want me and Jake to dig into on the call, drop it here ahead of time: https://forms.gle/NFJrZb3nc9xorgj5A Could be a build you're stuck on, a workflow you want us to look at, something you saw that you want our take on. Whatever's on your mind. We'll pull from these during the call so we can actually go deep instead of scrambling. See you there!

Just got my computer in an hour ago gonna start building out my folder system. I’m building systems to help trades men and blue-collar workers out pumped I found this community excited to create. Claude pro and clief notes premium! On the books today!! Pumped to start creating value to get on Claude Max and cliff Notes VIP!!! Any recommendations in any wealth of knowledge nothing but blessings to you, your journey and your buildout and the problems you’re trying to solve in your niche, nothing but domination and success for you and your loved ones! 🤙⚡️👊

New module just dropped in Implementation Playbooks. Claude Design: Folder Structure as a Design System Anthropic released Claude Design. It builds brand design systems, slide decks, prototypes, and animated content from your existing assets. Underneath the interface it is Claude Code, skills, and a folder structure. If that sounds familiar, it should. It is a refined version of what we have been building in this community. This module covers three things: 1. How Claude Design actually works, what it does well, and where it burns tokens fast. 2. How to export the design system it builds and run it locally in Claude Code or VS Code. 3. *Lightly Touches* on how to swap in open source models like Qwen 3 Coder Next, Code Gemma, Devstral, or DeepSeek Coder V2 when you hit usage limits or want to cut costs. Claude Design is not a replacement for the workflow you have been learning. It is proof the workflow is correct. The people who built Claude Design are solving the same problem with the same tools as you are here. The difference is you now have a head start, because you already understand folder structure, skills, and routing. If you are new here, start with Foundation Lesson 2 for the history, Lesson 4 for the install, and Implementation Playbook Module 1 for the animation builds that predate all of this. Watch the video. Build your own system this week. Post your folder structure in the community. Claude Design: Folder Structure as a Design System - Implementation Playbooks · Clief Notes

Open Session — April 2026 This is the full recording of our open session along with the slide deck version (Slide Deck in The Vault) What came up: The tools drop. Two small softwares a month, free to Premium and VIP, built from the asks in the early community thread. What qualifies, when they land, and why software is a commodity we share instead of sell. Alexander's case study. A commercial real estate firm in Grand Rapids gave him browser-only Claude for a one-month discovery budget. No IT, no integrations, no automations. One markdown file and a folder structure later, one handoff workflow saved roughly a sixth of Crystal's year and an estimated $10K on that single process. The architecture, the method, and the reason it worked without any of the usual AI tooling. Daniel's question. When to offload thinking to AI and when to keep it. What to sell and what to give away. Why copy-paste still beats premature automation, and why your competition becomes your development team the moment you understand how features ship. A project update on the voice prosthetic work. About the slide deck: The deck is the condensed, screenshot-ready version of everything in the session. Fifteen slides, one principle per slide, with a small "ASK" question at the bottom of each one. Those questions are the prompts. Screenshot any slide, drop it into Claude or your AI of choice, and it becomes the full prompt for that topic. This is the same pattern we use in the prompt library: questions that help you think, not outputs that think for you. How to use it: 1. Watch the session for the story. 2. Open the deck and screenshot the slides that apply to your current work. 3. Paste them into your AI and use the "ASK" prompt as the starting question. 4. Post what you find in the Premium discussion so others can learn from it. The transcript is also posted. If you pull something useful out of the deck or the recording, share it back. That is how this community compounds.

After watching the video and reading the companion: Vote below, then tell us in the comments: what is one task in your work that feels robotic? If AI handled it tomorrow, what would you do with the time?