the fitness log

Build your own · a starting point ·
July 2026

Build a dashboard like this for yourself?

This entire site started from one written request to Claude, then grew in stages — a live sync, a real domain, a daily health check — with every irreversible step held for approval along the way. Below is a version of that starting request you can copy, adapt to your own wearable or data source, and paste into a new Claude conversation.

I want to build a personal fitness dashboard that reads my real recovery, sleep, and training data automatically from my wearable's app (WHOOP, Oura, Garmin, Apple Health — whichever I actually use).

Here's the pattern I want it to follow:
1. Connect to my wearable's data through its official API, with my login handled securely on the server side and never exposed anywhere in the browser.
2. Publish a small, real website I can bookmark and check from my phone, showing my latest numbers. No login needed for me to view it day to day.
3. Sync on a schedule so it's never more than a day stale, without me having to ask.
4. Keep a plain Refresh button on the page for me to trigger a check on demand.
5. Build in a health check that runs after every update and tells me clearly if the data pipeline itself is broken — not just whether the numbers on screen look reasonable.
6. Be honest about the age of what I'm looking at — always show when a reading was last confirmed, rather than silently going stale.

Please help me scope this into a first small version we can finish today, tell me exactly what you'd need from me at each step (any account access, any purchase like a domain name, anything you can't do without my say-so), and don't do anything irreversible without checking with me first.
01

Claude asks first

Expect questions about what your numbers actually mean before anything gets built.

02

A first version, same session

A working, if small, version is realistic to see before the conversation ends.

03

You approve real-world steps

Connecting an account, spending money, or publishing something public always waits for your yes.

04

It grows in later passes

The domain, the daily health check, the auto-sync — all arrived after the first version, not in it. See the Roadmap for the real order.

How this actually gets maintained

All of this runs inside Cowork, working from a single project folder Claude keeps on your behalf — the code, the data, and a file called CLAUDE.md: Claude's own running notes on how the system works, decisions already made, and what's still open. Every new Cowork session reads that folder first, so it picks up exactly where the last one left off, and writes its notes back before it ends. You never have to re-explain the project from scratch, even months later.

You describe & approve Cowork does the work Live site what you see Project folder — CLAUDE.md + code persists on your computer, between every session reads first, writes back before it ends
Why Claude doesn't need the project re-explained each time.

Worth knowing before you start

Build in a daily health check from day one — it's the cheapest insurance you can add to a project like this, and far easier to set up before you need it than after. This exact dashboard's own check has already caught a stale data feed early more than once, instead of it going unnoticed for days.

Curious how this specific dashboard actually works? Read the Guide. Curious what order it was built in? Read the Roadmap.

The Fitness Log · Built with Claude