I’m 99% in goal with my private project: www.thewheelofclarity.com. This is something I’ve dreamed of for a long time—writing an e-book based on the teachings of a mentor. The original material was difficult to work with; it felt too spiritual and wasn't grounded enough for most people to actually use. I had a vision of making it simple and relatable, but getting there has been a long journey of trial and error. The Battle with "AI-Speak" I’ve tried to create this book several times. If you saw the first drafts and compared them to where I am today, you wouldn't believe it was the same book. The first many versions were done in ChatGPT, but I almost gave up several times. No matter how much we tried to improve it, the AI couldn't stay on track across all the chapters. I eventually switched to Gemini, and that’s where the version I have today finally took shape. But then I hit a wall with the "AI mindset." When I started looking at marketing, the AI kept insisting the target audience should be "high achievers" and "fast-paced CEOs." But that’s not what this book is. It’s for everyone—from stay-at-home parents to office workers to CEOs. It’s about understanding why certain patterns repeat in your life and how to change them. I ended up going through the book chapter by chapter to make it more human and accessible. Even after I thought I was done and created an audiobook version using ElevenLabs, I could still hear too much "AI" in it. It used words and phrasing that real people just don't use. I spent many nights listening to every single section, manually stripping out the "AI-isms" until it felt like my own. Building the Site with Claude Code The audiobook idea actually came from a colleague. I used ElevenLabs to find the right voice, and while you can still tell it’s AI, I’m proud of the voice I created and I’m sticking with it. For the website, I saw a video by Jake about folder structures in Claude Code. It sparked my curiosity, and even though I didn't fully understand the structure yet, I just jumped in. We built the site www.thewheelofclarity.com slavishly from top to bottom. We focused on one section at a time—brand voice, colors, and layout—until I was satisfied. Once the foundation was there, I added the technical side, like heatmaps and tracking tags, to help me optimize it later.

Just got around to watching the high tea session 2 and the discussion about workspace organization / management got me curious about what people are doing. For me I have a Top Level folder that is a Github repo, RL_MAP. I needed to work between 2 computers so I wanted built in sync and backup. Then within that only 1 CLAUDE.md at the root, and each workspace gets its own CONTEXT.md, root level just routes to each folder based on what I'm doing. All memory and context stored inside the repo, don't write to system memory and don't write system skills. This last part is evolving slightly as my needs are changing. The main global hook I have is I have claude auto-commit after each write, so I always have a backup and always can undo independent of Claude. Also makes looking at what changed very easy with Github's tools. This has worked for awhile but as you can see now its starting to get a bit crowded. The way Jake threw everything on the Desktop was kinda revelatory/mind blowing. But also as more and more of these small contexts appear in my work I'm seeing the benefit of not constraining everything to a single space. What have people found works for them?