Save a recipe with ingredients and servings

You just made the chicken curry — full recipe, 4 servings, lasts the week. You want to log a portion now and another tomorrow without doing the macro math each time, so you save the whole thing as a recipe with the ingredient list and the serving count.

What the agent needs to hear

Behind your sentence, the agent works backwards to three pieces: the recipe name, the number of servings it yields, and the ingredient list (food + quantity each). The serving count is what makes a recipe different from a saved meal: « 4 servings » means the agent computes per-serving macros from the ingredient totals divided by four, so a single-portion log later doesn’t have to re-do the math.

Ingredients get listed the way they would in any meal log — food name + quantity with unit. « 600 g chicken, 400 g rice, 200 g spinach » resolves three items. The agent shows you a card with the recipe name, the serving count, the full ingredient list, and the macros per serving — and waits for a nod before saving.

Servings and per-ingredient quantities

The serving count is the multiplier the system uses to scale macros. If your recipe makes 4 servings with 600 g total chicken, one serving is 150 g of chicken when logged. That math happens automatically — you never type 150 g for a per-portion log, you type « one serving of curry » and the agent fills the rest.

For ingredient quantities, use the totals of what went into the pot, not per-serving amounts. « 600 g chicken » means the whole recipe used 600 g, distributed across 4 servings. If you accidentally typed per-serving values (150 g chicken when you actually used 600 g across 4 servings), the per-serving macros end up off by the factor of servings. Total cooked quantities are the right shape; the agent divides for you.

Recipe vs saved meal

A recipe is for things you cook in batches and portion out: the curry, the chili, the breakfast prep you make Sunday for the week. A saved meal is a fixed combination of foods you eat as a unit (the post-workout shake is always whey + banana + oats, no portioning). The dividing line is whether the food gets divided into servings or eaten as one block.

If you find yourself logging « half a curry » or « a third of the casserole », that’s the signal for a recipe. If you log « my usual shake » or « the salad bowl » as a single item every time, that’s a saved meal.

When the agent gets it wrong

The card is where you catch mistakes. If the serving count is off (you said 4, the agent recorded 1, multiplying per-serving macros by 4x), call it: « 4 servings, not 1 ». If an ingredient quantity is wrong — you said 600 g chicken but the agent read 60 g — name the ingredient: « chicken was 600, not 60 ».

If the agent missed an ingredient (you mentioned coconut milk in passing but it didn’t make the list), add it: « also include 400 ml coconut milk ». The macros per serving recompute on the fly. And if the recipe name collides with an existing one (« chicken curry » is already in your library), the agent asks whether to update or create new.

What makes the recipe worth keeping

Three things decide whether this recipe is useful for the rest of the week: the serving count matches reality (a 4-serving recipe stored as 1-serving will quadruple every per-portion log’s macros), the ingredient quantities are totals from the pot, not per serving (the math runs in the right direction this way), and the ingredient list is complete (a forgotten oil or spice mix may not move calories much, but a forgotten 400 ml of coconut milk absolutely does). The system reads recipes as a per-serving macro lookup for every future log; one wrong field corrupts every portion log of that recipe until you fix it. Cook once, save once, log many.