Update food-tracking skill: always include nutrition in food log entries for non-medicine types
This commit is contained in:
parent
13053168a0
commit
87a5ca6555
1 changed files with 1 additions and 0 deletions
|
|
@ -96,5 +96,6 @@ uv run --with pymongo "$SCRIPT" update --id "6a11a937..." --unset unit
|
||||||
- When logging food, the assistant should run `food_items.py get --name <item>` first to confirm the item exists and show its nutrition info.
|
- When logging food, the assistant should run `food_items.py get --name <item>` first to confirm the item exists and show its nutrition info.
|
||||||
- For new foods not in the catalog, add the item first, then log it.
|
- For new foods not in the catalog, add the item first, then log it.
|
||||||
- Always present nutrition info back to the user when logging food (pull from `food_items` so the user sees the macros).
|
- Always present nutrition info back to the user when logging food (pull from `food_items` so the user sees the macros).
|
||||||
|
- **Always include nutrition info in food log entries** for any non-medicine type. Use `--extra` with a `"nutrition"` JSON object containing the relevant macros (calories, protein_g, fat_g, carbs_g, fiber_g, sugar_g, etc.) pulled from the food item's catalog entry.
|
||||||
- When searching the internet for nutrition facts, use USDA FoodData Central as the source, then store the result as a food item.
|
- When searching the internet for nutrition facts, use USDA FoodData Central as the source, then store the result as a food item.
|
||||||
- The `--extra` flag on both scripts accepts arbitrary JSON, useful for fields not covered by named flags (e.g., recipe details, tags, notes).
|
- The `--extra` flag on both scripts accepts arbitrary JSON, useful for fields not covered by named flags (e.g., recipe details, tags, notes).
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue