NutriCore — the spec

A personalized client portal that turns a user's body metrics and health goals into precise daily macro and micronutrient targets, then tracks every meal against those targets in real time. Built for everyday people who want a clear, science-backed number to hit each day — not another generic diet plan.

Decisions locked

The core loop

1. User creates an account and enters body metrics (age, weight, height, sex, activity level).
2. User sets a health goal (fat loss, muscle gain, maintenance, etc.); the system instantly calculates personalized macro and micronutrient targets.
3. User logs a meal by searching the food database; macros and micros auto-populate from the nutrition data.
4. Dashboard updates in real time, showing remaining targets for the day across all nutrients.
5. Micronutrient gap logic flags which nutrients are consistently under-hit and adjusts daily targets accordingly.
6. User changes a goal or updates metrics; the plan refreshes instantly to reflect the new numbers.

v1 scope

Auto-calculate macros from body metrics
Uses standard validated formulas (e.g., Mifflin-St Jeor for TDEE) applied to the user's entered metrics to produce a precise daily calorie and macro split. Lives on the onboarding flow and the Profile screen.

Goal-setting with instant plan refresh
User picks a goal and a target date; the system recalculates the entire nutrient plan immediately without requiring a support ticket or manual review. Lives on the Goals screen.

Food database with nutrition data
A searchable database of foods returning macro and micronutrient values per serving. Powers the meal logging flow; supports custom serving sizes.

Meal logging with auto-macro calculation
User selects a food and serving size; the entry is added to the day's log and all macro/micro totals update instantly. Lives on the Dashboard / Daily Log screen.

Daily micronutrient targets based on gaps
Tracks vitamins and minerals separately from macros, identifies where the user is consistently falling short, and adjusts recommended daily targets to close those gaps. Lives on the Nutrient Detail panel within the Dashboard.

Deliberately later

• Progress charts vs. personalized targets — charting is high-value only after users have accumulated enough logged days to make trends meaningful; ship in v2 once retention is proven.
• Weekly trend analysis and adjustments — automated weekly recalculations require a reliable baseline of behavior data that v1 will be building; add after the first cohort completes a full week.
• Export plan as PDF or share — a sharing feature assumes users have results worth sharing; prioritize after the core loop is sticky.

Data model sketch

• users — id, name, email, password_hash, created_at
• body_metrics — id, user_id, age, sex, weight_kg, height_cm, activity_level, recorded_at
• goals — id, user_id, goal_type, target_date, created_at, is_active
• nutrient_plans — id, user_id, goal_id, calories, protein_g, carbs_g, fat_g, micronutrient_targets (JSON), generated_at
• foods — id, name, serving_unit, calories, protein_g, carbs_g, fat_g, micronutrients (JSON), source
• meal_logs — id, user_id, food_id, meal_type, serving_qty, logged_at
• micronutrient_gaps — id, user_id, nutrient_key, rolling_avg, adjusted_target, updated_at
• payments — id, user_id, amount, currency, status, provider_reference, created_at

Screens

• Onboarding / Metrics Entry — collects body metrics and fires the initial plan calculation.
• Goals — lets the user set or change a health goal and shows the refreshed plan immediately.
• Dashboard / Daily Log — central screen; running macro and micronutrient totals against targets, plus the meal log for the current day.
• Meal Search & Add — food database search with serving-size picker; submits entry back to the Daily Log.
• Nutrient Detail Panel — expanded view of micronutrient intake, gap flags, and adjusted daily targets.
• Profile — edits body metrics, account details, and subscription/payment status.

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screens are defined; no interpretation required.
• Keep it as the single source of truth while you build, so every feature decision traces back to one agreed-upon reference.