Cronometer Diary

Use this skill when the user asks to track food in Cronometer, add diary entries from dictation, or improve the mapping between real products and Cronometer foods.

Goal

The user's preferred workflow is voice-first: they weigh food in the kitchen, dictate items such as "Breakfast, 50 grams oats, 10 grams flaxseed", and expect Cronometer Diary to be filled without manually using the app. Keep the spoken interaction short. Ask follow-up questions only when needed to avoid materially wrong entries.

Source Selection

Prefer Cronometer entries with broad micronutrient coverage while staying close to the food actually eaten.

Source priority:

1. NCCDB when a generic entry is a close match.
2. USDA when no suitable NCCDB match exists.
3. CRDB or branded/barcode entries when the product is processed, fortified, recipe-specific, or the generic macro profile is too far from the real product.

Do not choose a richer entry if its macros are materially unlike the consumed product. For example, do not map a fatty salmon product to a lean salmon entry just because the lean entry has more micronutrients. If the tradeoff is unclear, explain the options and ask the user which to use before saving.