Glad you're here. I'm Kevin, an ultrarunner & triathlete (Leadville 100 was my most fun race). I'm not a tech guru. I got curious about AI, realized I could build training tools tailored exactly to me from my own data, and it actually worked. Now I want to teach you to do the same and connect with people building cool things in fitness with AI. That's the whole idea: learn something genuinely interesting, build stuff that's truly yours, and do it alongside like-minded people. Zero coding required. Five steps to start: 1. Introduce yourself in the feed. Something like: "Hi, I'm Steve, I run trail ultras and can't wait to build with AI!" 2. Complete the intro poll so we know we can build the content around what you want: Athlete AI Poll 3. Watch Start Here course (top of the Classroom). Two minutes. 4. Do Day 0 in the 7-Day Challenge: Set Up Your Workshop. 5. Post in Wins as you finish each day, tagged (#Day0Ready). We celebrate every one. The setup day is the hardest part, and we get everyone through it. Stuck? Post what you tried and someone (often me) will get you unstuck. Let's build. Follow the road to The Rut.

This is a question I have gotten a couple times and I recently just went through this myself. If you are like me, you feed EVERYTHING into your OS. It's become my life operating system at this point, but AI is changing so fast and these models are improving by the second that what we did a couple months ago can became out of best practice for today's models. So I went through the exercise of cleaning mine up. Because I love ya'll, I built a guide for how you can do the same. It works like: 1) Measure what loads every session 2) Trim up the Claude.MD file 3) Put files exactly where they should be 4) One fact, one home - don't put things in multiple spots it confuses the models (use /doctor prompt-audit to perform an actual audit) 5) Build a recurring loop to audit the OS after each new model release Let me know how it goes and hopefully this helps some folks! @Jonathan Tauber if you are still working through updating yours, this might help! Kevin

If you're building your next training block by typing "give me a 20-week half Ironman plan" into ChatGPT, you're getting a generic template. It doesn't know what your last block looked like or where you fell apart. Here's how I built my plan for Ironman 70.3 Gulf Coast (sub-5 in May @Luis Velasquez, @Steven Holland and @John Drucis let's do this!) with Claude Code: 1. Reset my CLAUDE.md and athlete profile (same steps as yesterday's How to Tune Up Your AI OS guide), then pulled the full history of my last block straight from Garmin 2. Set my A race and goal, then had it work out the gap on every leg (about 40 min on the bike, 40 on the run, 5 in the swim) 3. Had it research programs the best in the sport already trust (I went with NVDM Triathlon) and break the block into phases, starting with a test week 4. Synced the whole plan to my watch, so I never enter a workout by hand 5. Tied my nutrition to my training: a deficit on easy days only, fuel on the hard ones, so I get leaner and stronger at the same time Full guide with every copy-paste prompt here: Build Your Next Training Block With AI. @Julia Kondrashkina @Pieter Wiese @Erik N here ya go! Want me to build it for you? Book a call about Athlete AI Mastery What's your next A race? Drop it below. Kevin

For years my lifting and my endurance training lived in two different places... my run plan had no idea I squatted heavy the day before lol. Most of you know the API already, but quick version: it's how two apps talk to each other. Garmin has one, Hevy has one, and Claude Code can read both. So for my 70.3 block I pulled both in and built the plan from there: 1. Pulled 6 months of swim, bike and run from Garmin and every lift from Hevy, then had Claude lay them side by side, day by day 2. Wrote the rules for how the two work together - heavy lifts never land on a hard bike day, endurance first then lift, and lifting drops from 2x to 1x a week once the long sessions come in 3. Built one week with both: Zwift intervals Tue/Thu, heavy lifts Wed/Fri, long session Sunday 4. Lifts go to Hevy with each week's weights (70/75/80/60% waves), swim/bike/run goes to my watch 5. Every Sunday it pulls both, checks them against the plan and updates next week's weights Full guide with every prompt here: Combine Strength and Endurance Training With AI Want me to build it for you? Book a call about Athlete AI Mastery Curious how everyone's fitting lifting in this winter, let me know! Kevin

I've tried half a dozen calorie trackers and none of them ever talked to my training... so I built one into my fitness agent. I just text it what I ate on Telegram (or snap a photo of the plate or the barcode) and it looks the food up in the USDA database, logs it and tells me where I'm at for the day. Logged my first meals this week and honestly it's pretty easy. The cool part is everything lands in the same place as my workouts, weigh-ins and sleep. Here is how it ties together: 1. Easy day, it runs my cut. Hard or long day, it makes sure I'm actually fueled 2. If I'm losing weight too fast, it tells me to eat more 3. Bad sleep or high resting HR, it suggests an easier session 4. My 5:30am brief has yesterday's food right next to today's workout This has the complete context of my training, goals and nutrition so its basically a nutrition brain for your training 🧠. Full guide here: Build Your Food & Nutrition Brain. Build this into your Athlete OS and let me know if you find out anything cool about your fueling! Kevin