How Claude Gets Better the More You Train Together

Most training tools treat every session as isolated. You log your run, see some numbers, and start fresh the next day. Claude is different. Used properly, it builds a picture of you as an athlete over time, your patterns, your tendencies, what works for you, and what does not.

This does not happen automatically. It requires a small amount of setup and a consistent habit of working with Claude in the right way. This article explains how.

Set up a Claude Project for your training

The single most important thing you can do to make Claude more useful over time is create a dedicated Claude Project for your training.

A Claude Project is a persistent workspace in Claude where you can store background context that Claude reads at the start of every conversation. Instead of re-explaining who you are and what you are training for every time you open a new chat, Claude already knows.

To set it up, go to Claude.ai and create a new Project. Call it something like "Training" or "My Running."

In the Project instructions, sometimes called the system prompt or custom instructions depending on your Claude plan, add a short profile of yourself as an athlete. Something like:

I am a self-coached runner training for [goal event]. My threshold pace is approximately [X] per km. My Critical Power from Stryd is approximately [X] watts. I train [X] days per week with a long run on Sundays. I am currently in [base building, build phase, taper, recovery]. I use Intervals.icu and IcuSync to push workouts to my Garmin.

Update this whenever something significant changes, a new goal race, a fitness test result, a change in training availability.

Every conversation you have inside this Project will start with Claude already holding this context. Over time, Claude also builds memories from your conversations that carry forward automatically.

Let Claude challenge your Intervals.icu defaults

Your Intervals.icu threshold pace and Critical Power are starting points, not gospel. They are set at a point in time and may not reflect your actual current fitness, especially if your training has progressed significantly or if you have not done a formal test in a while.

One of the most valuable things Claude can do is notice the gap between what your settings say and what your data actually shows.

Ask Claude to audit this for you:

Look at my recent race results and training data. Does my current threshold pace in Intervals.icu still look accurate, or does the data suggest it needs updating?

Claude will read your recent activities, look at the paces you are hitting in threshold-range efforts, and give you an honest assessment. If your threshold pace is set conservatively relative to what you are actually running, Claude will tell you, and workouts it generates will feel too easy until you update it.

The same applies to Stryd Critical Power. Stryd updates your CP automatically in the Stryd app as your fitness changes, but you need to manually update it in Intervals.icu for Claude to use the correct value. Ask Claude to flag this:

Based on my recent Stryd data and training, does my Critical Power in Intervals.icu look current? Should I update it?

Claude will compare what it sees in your activity data against your stored CP and tell you whether the two are aligned.

Agree on your approach and tell Claude

Claude works best when it understands not just your data but your training philosophy. If you have a view on how you like to train, how you approach easy days, how conservative or aggressive you are with load, whether you prefer feel-based or data-driven decisions — tell Claude and store it in your Project.

For example:

I prefer to build load conservatively. I would rather undertrain slightly than accumulate too much fatigue. If my fitness and fatigue look close, always recommend the easier option.

Or:

I respond well to higher volume and recover quickly. I have historically been able to handle more load than standard recommendations suggest. Factor this in when assessing my training.

Once Claude has this context stored, it applies it consistently across every session it builds and every assessment it gives. You stop getting generic advice and start getting recommendations that fit how you actually train.

Build an ongoing conversation about your progress

The most powerful way to use Claude with IcuSync is as an ongoing coaching conversation that develops week by week, not a series of one-off requests.

At the end of each week, do a short review conversation in your Training Project:

Here is how this week went: [brief notes, what you hit, what you missed, how you felt]. What does this tell you about how my training is progressing and what should next week look like?

Give Claude the subjective context it cannot get from your data alone. How your legs felt. Whether you were stressed or tired outside of training. Whether a session felt harder or easier than the numbers suggest.

Over weeks, Claude builds a progressively richer understanding of how you respond to training. It will start to anticipate things, noticing that you tend to struggle in weeks three of a build block, or that your pace data always looks worse than your effort felt, or that you recover faster than your fitness curve suggests.

This is what good coaching looks like. Claude is not replacing it, but it is a meaningful version of it, available any time, using your actual data.

What to store in your Project over time

As you accumulate training history with Claude, keep your Project instructions updated. Useful things to include:

Your current training phase and goal event with date.

Your most recent threshold test result or CP value, and when you last tested.

Any injuries or recurring issues Claude should factor in when building sessions.

Your agreed training philosophy, conservative or progressive, feel-based or data-driven, how you handle missed sessions.

Key findings from past reviews, for example, "I tend to accumulate fatigue quickly in week three of a build block" or "I respond better to more frequent shorter runs than fewer longer ones."

Your device setup, Garmin or Coros, whether you use Stryd, what sport settings are current in intervals.icu.

The more accurate and current this context is, the more specifically Claude can respond. A Claude that knows you have a history of Achilles tightness, prefers conservative load management, and is eight weeks out from your goal marathon will give you very different advice than one starting from scratch.

A realistic view of what this takes

This approach requires more than just installing IcuSync and asking Claude to build a workout. It requires treating your training conversations as a practice, showing up weekly, giving Claude honest context, and updating your Project as things change.

The payoff is a training tool that genuinely adapts to you over time. One that questions your settings when the data suggests they are wrong. One that remembers what you agreed last week. One that gets more useful the longer you use it.

That is not something any static training app can do. It is what makes Claude a fundamentally different kind of training partner.