Locked in for the next 5 days only. Ends May 5th at 10:00 AM EST. No exceptions. 🎉 Premium: $27 → $14/mo 🎉 VIP: $97 → $67/mo The closest you'll get to our original launch pricing. We're doing this because the community has shown up for us, and we want to show up back. 🤝 🔥 Already a member? Read this carefully. To lock in the new rate, you need to: 1. Cancel your current plan 2. Resign under the new price That's the only way the system can apply the new rate. We have way too many members for manual refunds, so we can't refund anyone who just signed up at current pricing. But the savings stack month over month, so if you plan to stick around (and you should 😁), the math works out fast. 🚫 A few ground rules: Please do not DM myself or Jake about pricing, exceptions, or extensions. We love you, but we're a small team and we need to stay focused on building. Everyone gets the same window. Everyone gets the same deal. If you miss it, you miss it. We'll do more things for the community down the road. ⏰ The clock: 🟢 LIVE NOW 🔴 Locks May 5th, 10:00 AM EST - Premium gets you The Vault and Afternoon Tea calls. - VIP gets you The Drawing Room, High Tea, and bespoke folder builds from Jake himself. If you've been on the fence, this is the moment. 🚀 Tag a friend who needs to be in here. Let's make Cinco a movement. 🎊 🌶️🌶️🌶️

for people just starting, here's what I did to start organizing my file system after a few days of use. I have a little bit of coding background so I asked claude to treat my file system like computer architecture and follow SOLID principles. They are roughly summarized as follows: - Separation of concerns — each file has one job - DRY (Don't Repeat Yourself) — data lives in one place - Single source of truth — no two files own the same information - Load only what you need — frequently accessed files stay shallow and small As example my claude.md file shrunk about 50%, it had grown from 30-40 lines to 100 or so. And the context file in another workspace went from 157 lines to 15. The goal isn't necessarily file reduction, it's efficiency and clarity. I went step by step through each directory with Claude to clean up stuff. At the end I had Claude summarize the process for me to share. attached are pictures of the .md file for easy viewing and I included the actual .md file of the process. But I'll also list it below: The Process Every refactor follows the same pattern: 1. Audit — list every job the file or directory is currently doing 2. Identify what's wrong — duplication, mixed concerns, wrong location 3. Propose before acting — show the before/after and confirm scope 4. Execute in order — move files first, update references second 5. Verify — make sure all links and paths still resolve The key question at each step: does this file have one job, and does it live where you'd naturally look for it? Prompts Used The actual prompts from this session, mapped to each process step. Audit "look at Claude.md architecture. analyse for separation of concerns and good computer architecture" "let's look at sound design context file first" Identify violations "looking at Claude.md Identity, workspaces and routing section. Is there overlap of function there?" "as a computer system architect taking into account separation of concerns, DRY, and clarity, what is the most efficient format?"