EYYYYY I'm an entrepreneur based in Miami. Over the years I've scaled multiple projects to 8 figures and built communities with several million followers combined. I mention this only to give context about the scale I'm operating at day-to-day. Right now I'm migrating my ENTIRE operation to Claude. Not just isolated tasks — I'm designing a global architecture from scratch that includes: - A "mother project" that orchestrates my whole life and businesses - Subprojects for each company/client I collaborate with - A daily personal assistant that reviews my goals, routines, and decisions - Reusable global skills (proposals, meeting notes, content, etc.) - Local skills only when the project context justifies it - Automated workflows for the tasks I do repeatedly The philosophy I'm building on: a minimal root CLAUDE.md (more of a "map" than a container), dense context at lower levels, skills with lazy loading so I'm not burning tokens unnecessarily, and a clear separation between tools (scripts), workflows (procedures), and skills (packaged expertise). My question for the community: What architectural decisions did you make that you later wished you'd done differently? I'm especially interested in hearing from those of you who have already been running Claude Code at real scale for months — not the YouTube tutorials, but the painful lessons that only come from daily use. A few things I'm specifically debating: 1. Global skills by default and local by exception, or the other way around? 2. How do you balance automating everything vs keeping manual control on critical decisions? 3. Which daily workflows gave you the biggest ROI from day one? 4. Any expensive early mistake you can help me avoid? I'm planning to document the entire process and I'm happy to share the learnings with the community as I go. The idea is for this to also serve as a case study for other entrepreneurs who want to do the same. Thanks in advance to anyone who takes the time to reply. Comments are worth gold at this stage 🙏

Andrej Karpathy just shared his method for building LLM-powered knowledge bases using nothing but markdown files and Claude Code. In this video, I walk you through exactly how to set it up in about 5 minutes using Obsidian as a front end. I also show you two of my own wikis, one for YouTube transcripts and one for my personal second brain, and break down how this compares to traditional semantic search RAG. https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f https://ai-2027.com/

Go to YouTube right now. What's the most talked about tool? Claude. In March alone, Anthropic dropped 10+ new Claude features. While n8n has lost its spot in the limelight. Guess what's happening in the background though? It's still growing on GitHub. When I started with n8n in October, they had 150k stars. Now? 180k. And this is from folks who go into GitHub and star it. Think of all the people creating an account right now and not login into Github to give them a star. This is why I'm not panicking about the Claude craze. And just so you know businesses are still using Zapier today. It's not about the tools. It's about solving problems. Here's some food for thoughts: I've worked with 35+ clients for the past 6 months. Not one person has asked me to build with Claude. I still use Claude to help me build, but they did not care when I built... - A lead nurturing system for WhatsApp. - A customer service AI agent. - A Meta ads AI bot that analyzes your ads. They didn't ask me about Claude. They had a problem and asked me to solve it. I gave them suggestions on what to use and they said "ok, cool, let's fix it". So if you think you need to use Claude or you'll fall behind, you won't. Not as long as you can solve real business problems.

Let's get to know each other! Comment below sharing where you are in the world, a career goal you have, and something you like to do for fun. 😊

From first client handoffs and SaaS traction to Claude-powered systems and internal tools - this week inside AIS+ showed what happens when builders focus on solving real problems and shipping fast. 🚀 Standout Wins of the Week inside AIS+ 👉 @Patrick Florencio built and deployed his first Claude Code ATS app, now used across a portfolio of 15 companies. 👉 @Dion Wang completed his first full client handoff after months of consistent building and refinement. 👉 @Bill Scully eliminated days of manual work by building an SEO migration evaluation agent. 👉 @Tobias Bielke got his first paying SaaS user, turning an idea into a real product with traction. 👉 @Debbie DeMarco Bennett built a forum scheduling automation handling 37 topics in under 2 minutes — plus launched her AI executive assistant. 🎥 Super Win Spotlight | @Diane McCracken Diane joined AIS+ during a difficult phase in life - with one clear goal:figure things out and rebuild. Since joining, she has: • Transitioned her business into a scalable, AI-driven model • Built multiple AI agents (now on her 4th iteration) • Integrated Claude deeply into her workflows and operations • Set a clear goal: rebuild to $10K/month and scale to $100K/month Her biggest shift? From doubt and uncertainty → to full commitment and action. Diane’s journey is proof that it doesn’t matter where you start - what matters is how quickly you decide to go all in. 🎥 Watch Diane’s story 👇 ✨ Want to see wins like this every week? Step inside AI Automation Society Plus and start building assets that compound 🚀