My health-system passion project, and the app that started my whole journey into vibe coding.
Vitality Quest began on Replit as a simple way to track my supplements. Then I added habits. Then sleep, workouts, nutrition, labs, quests, analytics, and all the little connections between them. It kept growing because I kept using it and kept learning what AI-assisted building could do.
I moved the project from Replit to Claude Code, and now to Codex, because it has become my playground for learning new AI development workflows. It probably has too many modules and too many components right now, and I will eventually slim it down. But it is also the most useful thing I have built with AI because I use it every day.
Every module writes to the same underlying model. That is what makes cross-domain insight a first-class query instead of an ad-hoc report. Today Hub at the top of the day, Analytics at the bottom, everything else orbiting the person using it.
Vitality Quest is not a product you graduate into. You start with four modules or you start with twenty, and the system scales with you. Three honest entry points below.
Starting out
New to tracking, or starting over.
You want a few things to track, a place for your morning rhythm, and a sleep log that does not disappear into a spreadsheet. Start with four modules. Everything else stays off until you reach for it.
Optimizing
You want to know what actually works for your body.
You have been tracking for a while. Time to let the data talk back. Lab trends, a real supplement protocol, state-regulation practices, and cross-domain patterns the system starts surfacing on its own.
Operating a system
You run the rest of your life as a designed system.
Your health stack should run the same way. Full protocol libraries for long plans, bundles for fast starts, challenges for intensity phases, and cross-module analytics for real-time judgment. All twenty-two, on one schema.
Seven touches, none of them long. The app is the background. You are the practice.
Today Hub
Open the app. Three things due: morning supplements, a sleep log for last night, a gratitude entry. Done by 6:11.
Breathwork
Four minutes of box-breathing before the kids are up. Session saved. Pattern building.
Routines
Morning routine fires. Habits check off as you go. Water, journal, stretch, read for ten.
Nutrition
Log lunch. Note the energy dip you felt mid-morning. That note will show up next time Analytics looks at the week.
Exercise
Today's lift is already there. Last session's numbers, today's template, weights in. Logged and closed.
Routines · Gratitude
Evening routine starts. Prayer, one gratitude entry, a page of book notes. Wind-down you actually hit.
Sleep
Lights down. Sleep target met on the calendar. Tomorrow's Today Hub builds while you rest.
Most health apps track things in separate buckets. Vitality Quest runs all twenty-two modules against one schema, which means any question that spans domains is a first-class query instead of a custom report.
EXAMPLE RESULT · 90-DAY WINDOW
Ninety days of consistent supplements, four lifts a week, tighter nutrition, and daily habit adherence. Fasting glucose trended down. HRV trended up. Lipid panel improved. No single module surfaces that story. The cross-domain query does.
REPRESENTATIVE, NOT A BENCHMARK. THE REAL NUMBERS ARE YOURS.
Vitality Quest is where I learned how far I could push AI-assisted development when the feedback loop was real. I was not building a demo for an imaginary user. I was building something I opened every morning, adjusted when it annoyed me, and expanded when a new part of my health routine needed a home.
That is why it is both useful and overgrown. Some modules became daily infrastructure. Some were experiments that taught me what not to keep. The value of the project is not that every feature should stay forever. It is that building with AI let me explore, integrate, and learn fast enough to find the parts worth keeping.
Eventually I will slim it down. For now, it is the place where my health system and my AI-building practice keep teaching each other.
Twenty-two modules organized into four layers by the work they do. Inputs and substrates at the foundation. Daily behaviors in practice. Structured plans in strategy. Decisions and rewards at the synthesis layer. All on one data model so any cross-layer query is a first-class operation.
Foundations · 7 modules
The substrates your body runs on.
Sleep
Log how you slept. Watch rest shape your week.
Exercise
Programs, templates, sessions, records.
Nutrition
Meals, responses, elimination trials, patterns.
Supplements
Your stack as a real daily protocol.
Biomarkers
Lab trends over time, not isolated results.
Body
Baseline context everything else reads against.
Body Meas.
Change beyond the scale alone.
Daily Practice · 7 modules
The behaviors, run every day.
Habits
The things you decided matter, tracked honestly.
Routines
Morning and evening flows you actually run.
Breathwork
Regulation on demand. Over twenty techniques.
Prayer
Focus areas, answered prayers, continuity.
Gratitude
Structured reflection, revisited over time.
Books
Reading that keeps influencing after the last page.
Quote Review
Spaced repetition over your best highlights.
Strategy & Programs · 4 modules
Structured plans, run over time.
Health Opt.
Evidence-informed library. Nineteen categories, 190+ protocols.
Bundles
One-click starts for common goals.
Protocols
Multi-week plans. Daily steps, check-ins, adjustments.
Challenges
Time-bound intensity. Commit, track, finish.
Synthesis & Today Hub · 4 modules
Where the system talks back.
Today Hub
The short list of what matters right now.
Analytics
Cross-domain views. Trends. Patterns.
Achievements
Milestones and streaks that make progress visible.
Settings
Shape the app to your profile and preferences.
Stack
TypeScript, Supabase, one data model.
TypeScript end to end. React on the client, Express on the server, Drizzle for database mapping, and Supabase underneath. The important choice is not the tooling itself. It is that the modules write into one connected data model, so cross-domain patterns can be explored from one place.
Status
In production.
Used today by a small number of families. All twenty-two modules shipped. Continuous development as real daily use surfaces what matters and what does not.