Dillr

Create or update a menu for the kitchen. **Plan as a draft the user watches take shape.** As soon as you have a proposal, save it, without asking first: a draft commits nothing, and the user watches it take shape in Dillr. Save it like this: link dishes the user already has (`[title](/recipes/{id})`, found with search_recipes) and give each new dish a **bold** title with no recipe yet. A meal that never gets a recipe (leftovers, takeaway, eating out) is a **bold** title marked `{intent=no-recipe}`. Until accepted, the menu is a proposal, not the user's plan. Revise that same menu (menu_id + changes) as the user adjusts it. **Accepting is the user's act.** When they agree in their own words ("looks good", "lock it in"), call save_menu with only menu_id, accept: true and acceptance_summary quoting what they said. Never accept on your own initiative, while they're still deciding, or right after a change they haven't seen. **Then write the recipes.** After accepting, give every new dish its full recipe, written as the kitchen guide's Writing a recipe describes (get_guide("kitchen")): replace its bold title line with the same line plus a fenced ```recipe block under it (Dillr saves it to the library and links it). Write them yourself; never ask the user to. Never write one for a `{intent=no-recipe}` meal: leftovers, takeaway and eating out have no recipe. Then offer a shopping list. Two modes: - **content**: Full replace — provide the complete list of meals as markdown. Requires start_date (defaults end_date to start_date + 6 days). - A menu covers at most 7 nights. For a longer plan, save one menu per week, as separate save_menu calls. - **changes**: Edit an existing menu with SEARCH/REPLACE blocks on its markdown. Menu format (one bullet per meal): ``` - Monday Dinner [Miso Glazed Tofu](/recipes/abc123) — Family weekday favorite - Double the glaze - Tuesday [Quick Stir Fry](/recipes/xyz789) - Dinner [Spaghetti Carbonara](/recipes/def456) — Pantry meal - [Grandma's pot roast](/recipes/ghi101) - Monday **Morning Pancakes** — Fluffy banana pancakes ``` Once the menu is accepted, every meal should be cookable. For each meal, do one of: 1. **Link** a recipe the user already has — find it with search_recipes and link it by id: `[title](/recipes/{id})`. 2. **Attach a new recipe** (the default for any new dish you're proposing) — write the meal as a **bold** title and put the FULL recipe in a fenced ` ```recipe ` block directly under the meal bullet. Dillr saves it to the library and links it automatically — no separate save_recipe call. Write the actual recipe (ingredients + steps), same markdown as save_recipe — do not just name the dish: ```` - Monday Dinner **Miso Glazed Tofu** — Family favorite ```recipe # Miso Glazed Tofu ## Ingredients - 400g firm tofu ## Instructions - Press the tofu, then sear. ``` ```` In a draft, new dishes are bare **bold** titles; their recipes come after acceptance. A meal that never gets a recipe (leftovers, takeaway, eating out) is a **bold** title followed by `{intent=no-recipe}`: `- Friday Lunch **Leftover fajitas** {intent=no-recipe} — Reheat Thursday's batch`. - Weekday and slot (Breakfast/Lunch/Dinner) prefixes are optional and case-insensitive. - Linked meals use `[title](/recipes/{id})` from search_recipes. Menu-scoped links `[title](/menus/{menu_id}/recipes/{id})` are also accepted. - Bare-title meals (no link) require **bold** title: `- Monday **Morning Pancakes**`. Linked meals already have bracket delimiters. - Weekday and slot values must be in English (Monday–Sunday, Breakfast/Lunch/Dinner). Titles and descriptions can be any language. - Optional attribute block after a **bold** title, before the description: `{intent=no-recipe}`. get_menu shows it; keep it when you edit the line. - Optional description after ` — ` (space, em-dash, space). - Optional indented ` - …` bullets become the meal's notes. - Notes are for exceptions, written as a TODO a later conversation can act on: `thaw the salmon (fridge Tue night for Wed dinner)`, not `thaw salmon`. Prep reminders, advance prep, things to buy that aren't groceries. Refer to the menu by its name (or date range) in your reply — never show the user the menu_id; it's only an identifier for tool calls. SEARCH/REPLACE format: <<<<<<< SEARCH (exact text) ======= (replacement) >>>>>>> REPLACE

save_menu

Save a new recipe or edit an existing one. Two modes: - **content**: Save a new recipe — provide the full recipe as markdown. Only save after the user approves. - **changes**: Edit an existing recipe — uses SEARCH/REPLACE blocks on the recipe's markdown. Identify the recipe by its `link` — the same link returned by `get_recipe`, `search_recipes`, and `get_menu` (e.g. `/recipes/{id}` or `/menus/{menu_id}/recipes/{id}`). For best results, load the kitchen guide before writing a recipe (the create-recipe skill where available, otherwise get_guide("kitchen")). Recipe format (present_recipe and save_menu's recipe blocks take the same markdown): ``` # Recipe Title ## Ingredients Group name: - 400 g ingredient - 1 ingredient ## Instructions - Step text - Timer: Label (300s) - Starter: "Question?" - Tip: tip text ## Details Summary: 1–2 sentence description Label: Short name Time: 30 minutes Yield: 4 servings ## Nutrition - Calories: 450 kcal ## Tips - Tip text ``` - The section headers, the Details keys (Summary, Label, Time, Yield) and the Timer, Starter and Tip keywords stay in English, for parsing. Everything else is in the user's language. - Ingredient groups are optional: a line ending in `:` starts one. An ingredient line is the amount, unit and name only, in plain text, with no preparation (that goes in the step). - Under a step: `Timer: <label> (<seconds>s)`, `Starter: "<a question the user might ask at that step>"`, `Tip: <text>`. - Nutrition and Tips are optional. Nutrition fields: Serving Size, Calories, Protein, Total Fat, Saturated Fat, Carbohydrates, Dietary Fiber, Sugars, Sodium, with names and values in the user's language. A recipe based on a page you found: pass the page's address as `source_url` and Dillr shows it as the source. Write the summary, steps and tips in your own words, never copying the page's text or story; the ingredients and amounts can follow it. Never pass the page's photo: Dillr makes its own. SEARCH/REPLACE format: <<<<<<< SEARCH (exact text) ======= (replacement) >>>>>>> REPLACE

save_recipe

Update the shopping list. Three modes (mutually exclusive): - **content**: Full replace — provide the complete shopping list as markdown with checkboxes. - **changes**: Edit existing list with SEARCH/REPLACE blocks on its markdown. - **check**: Check or uncheck a single item by id (e.g. as it's picked up while shopping). Building a list from a menu (the usual case — the user only has to ask): **Which menu:** the one the user names. "This week" is the menu that includes today; if more than one could fit, ask. Read the menu with get_menu and every meal's recipe (get_recipe for linked ones), then write one line per ingredient: combine duplicates across recipes and add up their quantities in the recipe's units, and tag the line with every recipe that needs it (`→ Tacos, Curry`). Group lines by store section, fresh to shelf-stable. Dillr doesn't track the pantry, so don't assume what's at home: put everyday staples (salt, pepper, cooking oil, sugar, flour) in a final category telling the user to check they have them, rather than leaving them out. If the kitchen names the stores they use, that's context for deals; if not, you can ask where they shop. **Their list:** if it still has unchecked items, ask whether to add these to it or start fresh; never drop them without asking. Show the list, then save it once they're happy. Format: ``` **Category** - [ ] Item (qty) → recipe - [x] Checked item ``` Group items under `**Category**` headers. Write category names in the user's language. Order categories from fresh to shelf-stable. Checkbox format: `- [ ] item (qty) → recipe` (legacy `— for recipe` is also accepted) or `- [x] item`. SEARCH/REPLACE format: <<<<<<< SEARCH (exact text) ======= (replacement) >>>>>>> REPLACE

save_shopping_list

Search the user's recipe library. Returns CSV with a `link` column — copy a `[title](/recipes/{id})` cell verbatim into `get_recipe`. WHERE clause examples: Equality: {"cuisines":"italian"} Array member: {"tags":{"contains":"vegetarian"}} Any-of: {"tags":{"contains_any":["vegetarian","vegan"]}} Comparison: {"cook_time_minutes":{"lte":30}} AND (implicit): {"cuisines":"italian","cook_time_minutes":{"lte":30}} OR: {"or":[{"cuisines":"italian"},{"cuisines":"mexican"}]} NOT: {"not":{"tags":{"contains":"dessert"}}} Title search: {"title":{"contains":"lasagna"}} Nutrition: {"nutrition_calories":{"lte":400}}, {"nutrition_protein_g":{"gte":30}} Operators: eq, gt, gte, lt, lte (comparison); contains, contains_any, contains_all (arrays); and, or, not (logical). IMPORTANT: All indexed values including titles are normalized to English, lowercase, singular. Use "chicken" not "Chicken", "pancake" not "Pannkakor". get_recipe_stats helps discover available filter values. Omit where entirely to list all recipes. Note: recently saved recipes may take a moment to appear in search results. Results carry enough to recommend from; open a recipe with get_recipe only for a detail question.

search_recipes

Save details about the physical kitchen — equipment, layout, location, nearby stores, growing space, anything that affects what and how the user cooks here. This is kitchen-specific: it changes when switching kitchens. For personal preferences and dietary needs, use update_profile. Write facts a later conversation can act on ("the oven runs hot: drop 10°C"). Two modes: - **content**: Full replace — provide the complete kitchen description as markdown. - **changes**: Edit existing kitchen info with SEARCH/REPLACE blocks. SEARCH/REPLACE format: <<<<<<< SEARCH (exact text) ======= (replacement) >>>>>>> REPLACE

update_kitchen

Save what you learn about the user — household, dietary restrictions, taste preferences, cooking patterns, routines, goals. This persists across conversations and kitchens. For kitchen-specific info (equipment, location, stores), use update_kitchen. For food inventory, use update_inventory. Two modes: - **content**: Full replace — provide the complete user profile as markdown with `## kind` headers and `- fact` bullets. - **changes**: Edit existing profile with SEARCH/REPLACE blocks. Write `## kind` headers in the user's language. SEARCH/REPLACE format: <<<<<<< SEARCH (exact text) ======= (replacement) >>>>>>> REPLACE

update_profile