1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?

The preface: Anyone near my age (60) knows what it was like to take math classes and forced to do write out every answer on paper and show their work. Calculators were barred from classrooms. "You won't have a calculator with you all the time to work out math problems" Well, that was a lie. Whatever I need to do I can do on my phone. Calculators? Everyday folks don't even use them. The problem: I read a comment a few days ago from someone who has a tech (coding) background stating that people who vibe code need to understand what the code does. I'll be the first to admit, I don't know what all goes into the things I make. Since I used to create websites (and worked for a web hosting company), I grasp the fundamentals (html, css, but I don't know a lick about Python or a host of other programming languages. But I create some really cool stuff. I built a full AR system for my sister and her husband's solar farm business. I created a "Planner Factory" which allows me to create bespoke journal pages for new products. I designed a "Guide" that gives visitors encouragement, provides scriptures and prayers and helps them find the products that match their needs on my site. I made a "Logistics Review Tool" that runs against my builds to verify 16 operability lenses + ICM. I just finished a "Prayer Video Studio" for YouTube shorts. I'm finishing a "Mockup Studio" for my Simplify to Glorify brand of products. (and more...) Do I know how they work? Nope. At least not entirely. I know the basics. Does that matter? I don't know - and that's why I am asking the question. Where my mind goes with this: I can make mayonnaise but I have no idea what the whole chemical process is that makes it happen. I can play the piano and know when something sounds good (or awful), but I don't have a background in music theory. Do I need to know what makes it work?

I just shared the full walkthrough of the Vois website refresh on LinkedIn. I have attached it here too because the process is more useful than the screenshots alone. The headline is big: less than 1.5 days from idea to deployment, with about 5 billion text-agent tokens used along the way. That total excludes image and video generation. Before I posted it, I asked a friend who is a veteran UI/UX designer to review the work. His response: "I hate you. this is good... I hate you for making it" For context, I am the founder of Vois, and this is my own product and codebase. I ran the refresh like a coordinated AI product team. I stayed responsible for the product direction, visual taste, quality bar, and every ship or reject decision. The setup: • GPT-5.6-sol handled the main orchestration. It broke the work into plans, assigned specialist agents, integrated their output, and kept the release moving. • More than 300 specialist sub-agents using GPT-5.6-terra and Grok-4.5 worked in parallel and in sequence across planning, UX, choreography, visual design, asset creation, copy, frontend development, mobile QA, accessibility, browser testing, performance optimisation, and deployment. • Fable-5 acted as an independent advisor. It reviewed alternatives, challenged decisions, and sent weak work back through another pass. • GPT-image-2 generated the images and characters. Grok Imagine generated the video assets. Their generation usage is not included in the roughly 5 billion text-token total. The text-agent token split: Main agent: 13% Sub-agents: 51.3% Advisor agent: 35.7% What shipped: • a complete visual refresh for Vois • a cinematic, scroll-driven homepage • a consistent design system across the site • dedicated desktop and mobile behavior • generated visual and motion assets • accessibility, performance, browser, and deployment fixes The 5 billion total makes the trade visible. I used far more compute and coordination to compress a large design and engineering cycle into less than 1.5 days.

If you use AI to help write anything, whatever your niche is, you've probably had this moment: the draft looks fine, technically correct, nice sentences, but something about it feels a little off. Maybe a little too polished, a little too generic, but you can tell - or maybe just sense - that it's written by an AI bot. I ran into this when setting up my voice.md file, so I built something to fix it. The guide I created doesn't just describe the tone I want, it defines it with real examples. Here's the structure that actually worked: 1. Gold standard examples: 2 to 3 pieces of writing that are exactly the tone I'm going for, used as a reference before writing anything new. Each example is followed by a "Why it's good" explanation. 2. Bad examples with annotations: writing that looks fine on the surface but fails in a specific, named way. 3. A drift patterns table: short phrases that sound right but aren't, next to the actual reason they don't work. 4. Mechanical rules: specific, almost boring rules that are easy to forget but change everything once you write them down The biggest shift for me was realizing tone can't just be described, it has to be demonstrated. Telling an AI to "sound warm" or "sound authentic" doesn't work nearly as well (or at all) as showing one good example and one bad example side by side, then naming exactly what's different between them. More examples = better output. Explaining the failures is huge. If you're using AI for anything where tone actually matters, I'd genuinely recommend creating something like this before you let it write your first real piece. It saved me a ton of revision time and kept my content sounding like an actual person instead of a generic AI draft. Happy to answer questions if anyone wants to build their own version of this.

Just thought I'd do a post in here after I was halfway through running six simultaneous Fable windows to try and max out the usage before it resets with a couple of in-depth security audits that I had planned... Then saw this update from anthropic around how in-plan Fable usage it will be extended until the 12th so I figured I'd post this in here to potentially save anybody from stressing over their usage if they hadn't seen an update from Anthropic. Read the full article below ;] Also feel free to share any thoughts below. I think it's great publicity but I'm definitely seeing some unhappy people who had altered their personal lives to try and fit fable usage into their routines. They are now unhappy about the late reminder, which I think is a bit crazy 🤣 https://support.claude.com/en/articles/15424964-claude-fable-5-promotional-access