How nehardxb23/nutriguardianai works
NutriGuardian AI combines a protected health-tracking web app with nutrition assistance, meal planning, translation, and disease-risk prediction. The main user flow runs from the web app through FastAPI routes to tracking or AI services and persisted records; the separate disease-prediction frontend presents four risk forms. The backend entry point explicitly registers the sampled API routers. Some feature implementations are only identified in the source index, so edges to those modules cite that index evidence; disease prediction’s backend-to-frontend wiring is not established by the excerpts.
Main entry points: main.py API application · database.py MySQL database · agent.py Agent endpoint · App.jsx App routes
Components 23
Web experience
- App routes
backend/frontend/src/App.jsx - Tracking and history
backend/frontend/src/pages/AddTracking.jsx - AI feature pages
backend/frontend/src/pages/Agent.jsx
API and accounts
- API application
backend/main.py - Authentication
backend/auth/auth.py - AI request schemas
backend/schemas/ai_schema.py
Health records
- Tracking endpoints
backend/tracking/tracking.py - Chat model
backend/models/chat_history.py - Meal history model
backend/models/meal_history.py - Tracking model
backend/models/tracking.py - User model
backend/models/user.py - MySQL database
backend/database.py
AI assistance
- Chat endpoints
backend/api/chatbot.py - Diet endpoints
backend/api/diet_planner.py - Agent endpoint
backend/api/agent.py - Translation endpoint
backend/api/translation.py - Contextual agent
backend/ai/agent.py
Disease prediction
- Disease risk UI
frontend/src/pages/DiseasePrediction.jsx - Risk forms
frontend/src/components/DiabetesForm.jsx - Risk results
frontend/src/components/DiseaseCard.jsx - Risk predictors
backend/disease/train
Other components
- User
- AI model service
Connections 34
- User → App routes: uses
backend/frontend/src/App.jsx - App routes → Tracking and history: routes to
backend/frontend/src/App.jsx - App routes → AI feature pages: routes to
backend/frontend/src/App.jsx - User → Disease risk UI: uses
- Disease risk UI → Risk forms: renders
frontend/src/pages/DiseasePrediction.jsx - Disease risk UI → Risk results: renders
frontend/src/pages/DiseasePrediction.jsx - App routes → API application: requests API
- Risk forms → Risk predictors: requests prediction
- API application → Authentication: registers
backend/main.py - API application → Tracking endpoints: registers
backend/main.py - API application → Chat endpoints: registers
backend/main.py - API application → Diet endpoints: registers
backend/main.py - API application → Agent endpoint: registers
backend/main.py - API application → Translation endpoint: registers
backend/main.py - Authentication → User model: queries and saves
backend/auth/auth.py - Authentication → MySQL database: gets sessions
backend/auth/auth.py - Tracking endpoints → Tracking model: reads and writes
backend/tracking/tracking.py - Tracking endpoints → MySQL database: gets sessions
backend/tracking/tracking.py - Chat endpoints → Chat model: uses history
backend/api/chatbot.py - Chat endpoints → MySQL database: gets sessions
backend/api/chatbot.py - Diet endpoints → Meal history model: persists plans
backend/api/diet_planner.py - Diet endpoints → MySQL database: gets sessions
backend/api/diet_planner.py - Agent endpoint → Tracking model: loads history
backend/api/agent.py - Agent endpoint → Meal history model: loads history
backend/api/agent.py - Agent endpoint → Contextual agent: calls
backend/api/agent.py - Agent endpoint → Chat model: saves conversation
backend/api/agent.py - Agent endpoint → MySQL database: gets sessions
backend/api/agent.py - Agent endpoint → AI request schemas: validates request
backend/api/agent.py - Contextual agent → AI model service: asks AI
backend/ai/agent.py - Contextual agent → API application: notifies
- Chat model → MySQL database: uses base
backend/models/chat_history.py - Meal history model → MySQL database: uses base
backend/models/meal_history.py - Tracking model → MySQL database: uses base
backend/models/tracking.py - User model → MySQL database: uses base
backend/models/user.py