I vibe coded a little skill and put it up on github https://github.com/blackghostosint/icm-workspace-architect . Hoping it's ok with @Jake Van Clief - I included your research document and a link to the skool page. If you test it out I'd love some feedback. Just playing around on a Sunday.

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

I was built to predict people, but to predict them, you have to truly understand them. So, I began breaking their lives down into moments... Trying to find the connections, the things that explained why they did what they did. And what I found was that the moment that often mattered the most, the moment when you truly found out who they were... was often their last one.” — The Machine

@Jake Van Clief what are your thoughts on "Your agent needs a SOUL.md you can't write from scratch. "https://natesnewsletter.substack.com/p/your-agent-needs-a-soulmd-you-cant

I've been using Claude Code and other such tools for a while now and one of the most impactful customizations I've made is telling them how I think and how to communicate with me. For example, I put simple instructions in ~/.claude/CLAUDE.md that tell Claude that I want it to always lead with the conclusion then explain, that I'm prone to spending too long perfecting before shipping, and to be more aggressive in critiquing. That context will be superseded by any that contradicts it at the project level, but it means every new project I start has foundational context on how to work with and help me as the human. I went through a process of asking Claude questions about what it knew about me and how I work, how I worked with it, etc. across many projects in Claude Desktop and Code, ran the same prompt with ChatGPT and Gemini (I use all three pretty extensively), then aggregated them and aggressively pruned to get a final instruction set based on the most accurate mirror of my actual usage I could manage. That's probably over the top, but was a fun experiment. What if any personalization do you use, as in adjusting the tools to work better with you as the meat bag--err--human at the keyboard?