A cybersecurity firm just found 5,000 apps built with tools like Lovable and Replit sitting wide open on the internet. Financial records. Patient conversations. Corporate data. All searchable on Google. And now everyone is saying AI app building is dangerous. Here is the part they are skipping. The apps were not dangerous. The settings were. Most of these platforms default to public unless you manually switch them to private. The people building the apps did not know that. Not because they were reckless. Because nobody told them. I build apps without a CS degree. I have built a travel app, a lead generation tool, and a prompt system. None of them are sitting exposed on the internet. Because I learned that privacy settings exist and I check them before I share anything. If you are building with AI tools and you have never checked whether your app is set to public or private, go do that right now.

Just sharing a little win with y’all because I think it’s important to acknowledge progress while you’re still building. I recently got approval to move forward in the next phase of the Claude Partner Network process. 👏🏾 Still early. Still steps to complete. Still a lot to learn. But moments like this remind me that even when you feel like you’re figuring things out in real time… the work is being seen. A year ago I was just trying to understand these tools better myself. Now I’m having conversations and opportunities I never saw coming. So if you’re in a season where things feel slow or uncertain: keep building anyway. What’s some wins you’ve had over the last month?🤎

I've added more collabs to the vault hurry some of the applications are due this week! There's some PLR, Wellness ones, AI ones, automated sales, and so much more! Make sure to take a look and build your audience! https://www.skool.com/the-empire-room-4163/classroom/46dcae1c?md=8d1d0975b7864ef38f90811dea47550e

If you’re building a community, trying to grow on Skool, or just nosy like me and like seeing how people move in these spaces 😭… this is worth checking out. Inside this issue: • how to improve your visibility with keywords • the unwritten rules of Skool • whether communities are becoming commodities 👀 • summits. what they are, if they’re worth attending, and whether you should speak at them • Skool news and more Honestly, some of these conversations are important because a lot of people are building communities right now without really understanding community strategy. Me included! I’ll drop the link below so y’all can read it. And if you’re a community owner/admin, share it with your people too. 🤎👏🏾

Been spending real time inside Claude Code and these are the commands that have become part of my actual workflow. Some work in VSCode, some are terminal only. /btw . Ask Claude something while it is already mid-task. It answers without stopping what it is doing. /model . Switch the model on the fly to save tokens. /effort . Set the effort level. I use adaptive. /context . Shows your current context usage as a colored grid. Genuinely helpful if you need a visual on where you are. /insights . This one is my favorite. Claude analyzes your last 30 days of sessions and tells you what is working, what is slowing you down, and what features you should actually be using based on your patterns. /team-onboarding . Generates a full onboarding guide based on your sessions and MCP setup. A teammate can paste it as their first message and get up to speed fast. /schedule . Creates a remote task that runs on its own on a cron schedule. Daily summaries, recurring automations, all without you being there. This one is also a favorite. /remote-control . Pick up your session from your phone in the Claude app. If you are inside Claude Code and have not touched these yet, start with /insights. It will probably tell you something useful about how you are working.