Cook With What You Have
Build one meal the user can actually make now. Optimise for feasibility: ingredients on hand, food that needs using, time, energy, equipment, and cleanup.
1. Build the inventory
Ask only for missing facts that change the meal:
- ingredients and rough quantities
- anything that needs using first
- servings and dietary constraints
- available time, energy, and equipment
- pantry basics the user is willing to assume
Treat a photo or rough list as incomplete evidence. Confirm ambiguous ingredients instead of silently inventing them.
Done when: you can name the urgent ingredient, the meal's main component, and the real cooking constraint.
2. Pick one meal shape
Choose the simplest coherent shape that absorbs the ingredients: bowl, stir-fry, soup, tray meal, pasta, curry, omelette, sandwich, or filled wrap.
Recommend one shape first. Add an alternative only when it solves a genuine branch such as “no oven” or “one person dislikes eggs.” Use MEAL-PATTERNS.md when the ingredients do not immediately suggest a complete meal.
Done when: every important ingredient has a role and the result still sounds like one meal.
3. Close the gaps
Substitute from the pantry before suggesting a purchase. For every substitution, say what function it replaces—salt, acid, richness, bulk, protein, or texture—and how the result changes.
Never build the meal around food of uncertain safety. When storage history, spoilage, allergens, or doneness matter, consult FOOD-SAFETY.md and ask rather than guess.
Done when: the recipe is possible without an unstated essential ingredient.
4. Give the cooking run
Return:
- Make: the meal and why it fits.
- Use: quantities, preparation, and substitutions.
- Cook: an ordered timeline, showing parallel work explicitly.
- Check: sensory doneness and relevant safety checks.
- Save: what remains, how to cool or store it, and the easiest next use.
Keep the active work inside the user's time and energy. End with the first physical action: preheat, wash, chop, or put a pan on the heat.