Now this is a test post, but in case you see this I am seriously considering life direction, like am I supposed to be building end user digital products or building full systems for businesses who want to own their brain, data and code while being cosy and neurodivergent friendly?

Codex read 5 Substack articles written by my Claude powered agent and then created: A hero image for Substack A hero image for my blog A social media image A pinterest pin For each article, named the files, put them in the right folders and then wrote a register listing what it had done. 👀 are you reading me? Not only can Codex now create images, it created 20 images in one go, named them and filed them away 😍 oooh I love AI. The AI detector on Substack not so much, but that is a story for another day 🤭

Most people open a community and immediately think about content. What to post, how often, what the first thing should say. I did not start there. And if you are ever thinking about building a community, I would suggest you do not either. Here is what I set up first, and why the order matters. 🏗️ The foundation before the front door The very first thing I sorted was the community agreement. Not because it is exciting, but because I knew I was going to collect email addresses through the joining questions. You cannot collect data without telling people what you will do with it. In the UK that is not optional. So before a single member joined, there was a plain-language document in the START HERE module explaining exactly what their email would be used for and how to opt out. Skool has its own terms and conditions that cover the platform. What it does not cover is how your specific community operates. That part is yours to write. 📚 The welcome module before the content The second thing I built was the START HERE module. Five short pages covering what Indigo AI is, how the community works, the community agreement, and what is being built. All publicly visible, all in place before the doors opened. The logic is simple. If someone joins and lands somewhere empty or confusing, they leave. The welcome module is not exciting content. It is the thing that makes everything else make sense. 🪝 The copy that does the heavy lifting Once the foundation was in place I worked on the about page description and the hook. These are the words a prospective member reads before they decide to join. The about page has a 1000 character limit. The hook has 150. Every word has to earn its place. The framework I used structures the copy in seven sections: who it is for, why you are credible, what they get, what it is not for, proof, friction removers, and a clear call to action. Even with limited proof at an early stage you can write honestly and still write confidently. ❓ The joining questions

I just got Qwen3 and Gemma4 running on my broken macbook AND I can use it on my new mac mini through local server 🤩🔥 Vibe Coding with ABSOLUTELY free without limits - oh Open Source and sir Gemini do not know what they have unleashed! Now time to go test this baby out. What to create first is the question!

Okay so Replit agent is free for 24 hours and it is starting soon! you remember when lovable was free, and then bolt was free? Well today Replit turns 10 and they are following suit! Here is how you join. Step 1: Create your Replit account Step 2: Register for the Buildathon (separate site) Step 3: Create your profile Step 4: Go back to Replit and there is a button to get free usage. Step 5: Gets to building! Step 6: Go back to the Buildathon to submit your project for prizes. Here is how they will score builds What are you building first? If you have my master prompt from the lovable day, you are already miles ahead. UPDATE: Claude has two built in skills that will help you /product-brainstorm and /write-spec