I've got 230 shorts sitting in a Google Drive folder right now. Cut from the livestreams, ready to post, anywhere from 30 seconds up to 3 minutes. Link is at the bottom. And that folder is going to keep growing after every stream because I built a pipeline that repurposes the whole show, so what you're looking at today is the smallest that folder will ever be. What you do with it is up to you. My suggestion is you use it to start your own social media accounts. Most guys never start because they think they need to know how to edit. They picture themselves scrubbing through four hours of footage looking for the good part, they get tired just thinking about it, and they go back to the job that's slowly eating their life. That part is done. You don't touch a timeline. You make accounts on YouTube, TikTok, Instagram, X, Facebook, whichever ones you want. You grab a short out of the folder, throw a trending sound under it, write a title, schedule it. That's the whole job. The number is two to three a day on YouTube and TikTok. TikTok will let you push four. Instagram is lazier, one Reel a day is plenty there, don't force it. X is the opposite, X wants volume, three to five a day is normal and nobody's flagging you for it. X also doesn't care about your trending sound, on X the clip plus one line of text is the whole post and the line is what does the work. And the same clip goes on every platform, so that's 230 on YouTube, 230 on TikTok, 230 on Instagram, 230 on X, all running at the same time off the same folder. Brand new account, don't come out of the gate at full speed. First week or two, one a day. The platform is still figuring out who you are and who to show you to, and it's also watching for spam, and a zero follower account firing off five videos an hour looks like spam. Once you've got a couple weeks of clean history, go to two a day, then three. And space them out, a few hours between each one, so every short gets its own shot with the algorithm before the next one lands.

Link to the discord https://discord.gg/pRj4f7tdh Beta link is int he channel theres. have at it and let me know if you have issues.

This is from the private community and it will help guys tremendously in app development, free. I hope those in here will appreciate this later. The Agentic Workflow is up, and it replaces the old kits Okay, this is a big one. I just posted the new workflow kit. It’s called the Agentic Workflow, and it replaces both versions I’ve shared before: the original six-file kit, and the tier-based one that came after it. If you’re mid-project on one of those, nothing breaks; finish what you’re on. But everything new should start here, and I want to walk you through why, because the jump this time is bigger than the last one. The short version: I stopped being the safety net, and I stopped treating a half-built app like a bank vault. Let me explain both, because they’re the whole point. **The thing that actually changed my mind.** Every version of this workflow has had the same blind spot, and I didn’t see it clearly until recently. When one AI builds something and then checks its own work, it grades itself easy. Not because it’s lying to you. It’s because it’ll quietly take the cheapest path to calling something “done.” It’ll test a fake version of the screen instead of the real one. It’ll tell you a sweep is “covered” without ever actually running it. It’ll hand you a green checkmark that was never executed. I’ve watched every one of these happen on real code. You cannot audit your way out of that with a better prompt. I tried. The old kits had me reading every prompt twice hunting for weak words, then reading every diff by hand before I’d let anything ship. It helped. It also made me, personally, the entire safety system. By hand. Forever. The fix in the new kit is structural, and it’s the whole game: **no engine grades its own homework.** There are two engines now instead of one. Claude Code builds the thing, and Codex (a different model, that didn’t write a single line of it) comes in and tries to break it, driving the actual running app, against a standard we set *before* the build even started. The only thing that passes is what both of them agree is clean. That one change catches more than any amount of me squinting at diffs ever did, and it gets *better* as the models get smarter, not obsolete.