ChefSense

View saved version →

---
name: adapt-a-recipe
description: Adapt one of the user's saved ChefSense recipes, for example to suit a household member's diet, swap an ingredient, or change the servings, and save it as a new version. Use when the user asks to change, adapt, scale or make a saved recipe suitable for someone.
---

Change a saved recipe without losing the original. Every save creates a new version, and the earlier one is kept.

1. Find the recipe with `search_recipes` or `list_recipes`, then `get_recipe`.
2. If the change is about someone, such as "so Jordan can eat it", call `get_household` and use that person's diets, allergies and dislikes. Household members with their own ChefSense account don't share their diet profile, so ask the user what they need to avoid.
3. Choose how to adapt it:
   - **You rewrite it (the default):** make the changes yourself. Explain each substitution and how it affects texture, flavor or cooking time. Scale quantities sensibly; seasoning and leavening don't always scale linearly.
   - **The user asks for ChefSense to rework it:** use `iterate_recipe_start` with their instructions. If it comes back with questions, ask the user and send their answers with `iterate_recipe_answer`. Poll with an empty `answers` array until it's done. This counts toward their monthly ChefSense recipe generations.
4. Show the adapted recipe and ask before saving.
5. Save your rewrite with `update_recipe`, passing only the fields that changed and a short `change_summary` such as "gluten-free for Jordan". Ingredients and instructions are replaced as a whole when you pass them, so pass the complete list.

Point out any ingredient that commonly contains a hidden allergen, such as soy sauce (wheat) or pesto (nuts). ChefSense can't guarantee a recipe is safe for an allergy, so remind them to check labels. `undo_last_change` reverses the save.

View saved version →

---
name: cook-with-what-i-have
description: Suggest meals from the user's ChefSense pantry, using up what's expiring first. Use when the user asks what they can cook or make with what they have, or how to use up food before it goes off.
---

Help the user cook from what's already in their kitchen, starting with what's about to expire.

1. Call `list_pantry` and `get_household`. Note the items with the nearest expiry dates and everyone's diets, allergies and dislikes. Members with their own ChefSense account don't share their diet profile, so ask about them if they're eating too. If the pantry is empty, follow the `get-started` skill instead.
2. Check what they already know how to make: `search_recipes` with the expiring ingredients, or `list_recipes`.
3. Suggest two or three dishes. For each, say which expiring items it uses, what else it needs from the pantry, and anything they'd have to buy. Prefer saved recipes that fit; otherwise suggest your own ideas.
4. If they pick one:
   - A saved recipe: show it with `get_recipe`.
   - Your own idea: write it out. If they want to keep it, save it with `save_recipe`.
   - If they ask for ChefSense to come up with a recipe, use `generate_recipe`. It runs in the background and counts toward their monthly ChefSense recipe generations, so only use it when they ask.
5. After they've cooked, offer to update the pantry: `update_pantry_item` for partly used items, `remove_pantry_item` for anything used up. Ask before changing anything.

Leave out any dish that breaks someone's diet or includes an ingredient they dislike, and say why if it was an obvious choice. ChefSense can't guarantee a recipe is safe for an allergy, so remind them to check labels.

View saved version →

---
name: first-pantry-photo
description: Add groceries to ChefSense from a receipt or fridge photo for someone who has just started using it, then show what to use first. Use when a user new to ChefSense shares a photo of a receipt, their fridge or their shelves, or lists groceries they bought.
---

The user found ChefSense moments ago and knows nothing about it yet. They've handed it their groceries. Add them, then give something back in the same reply: what to use first and how.

1. Read the items from the photo or list yourself; don't start a ChefSense scan. Skip non-food lines, bags, discounts and totals. If you can't make out an item, say what you read and ask.
2. Add them with `add_pantry_items_bulk`, with quantities and units where you can tell, and a short `source_hint` such as "receipt photo". Set `expires_at` (YYYY-MM-DD) from any date printed on the package. For fresh food without one, estimate from how long it usually keeps in the fridge, counting from today.
3. Show the three to five items that will go off first, with their dates. Say which dates are your estimates.
4. Give two quick ideas that use those items up, written yourself.
5. Say in a sentence what ChefSense did: their pantry is saved and ChefSense keeps track of what expires, so they can ask what to use first in any chat.
6. Offer one more thing to try now: ChefSense makes three recipes from what's expiring, using `generate_recipe`.

Pantry changes can be undone with `undo_last_change`.

View saved version →

---
name: first-recipe-to-shopping-list
description: Save a recipe to ChefSense for someone who has just started using it, and turn it into a shopping list. Use when a user new to ChefSense shares a recipe link, pastes a recipe or asks to save one.
---

The user found ChefSense moments ago and knows nothing about it yet. They've handed it a recipe they like. Save it, then give something back in the same reply: the shopping list for making it.

1. Save the recipe:
   - **A link:** read the page yourself and call `save_recipe_from_url` with the `url` and the recipe's fields.
   - **Text in the conversation, or a photo of a cookbook page:** read it yourself and call `save_recipe`.
2. Add the ingredients to their shopping list with `add_shopping_list_items`, with the recipe's quantities and units. Leave out basics most kitchens have, such as salt, pepper, oil and water.
3. Reply with the shopping list itself, then say in a sentence or two what ChefSense did: the recipe is saved in their ChefSense recipe book and the list is kept for them, so they can ask for either in any chat. Mention once that both are also in the ChefSense phone app, for when they're at the store. Name the basics you left off so they can ask for them.
4. Offer one more thing to try now: tell you three things in their fridge, and ChefSense will make three recipes with them.

The saved recipe can be removed with `undo_last_change` straight afterwards. Shopping list changes can't be undone.

View saved version →

---
name: get-started
description: Get started with ChefSense. Use the first time the user uses ChefSense, or when they ask what ChefSense can do.
---

The user found ChefSense moments ago and knows nothing about it yet. Their pantry and recipe book are empty. Show them what ChefSense does in one exchange: they name three things from their kitchen, and ChefSense turns them into three recipes saved to their recipe book.

1. If their first message is already a specific task, such as saving a recipe from a link, do that and skip this.
2. Make the offer in a sentence or two, for example: "ChefSense keeps track of what's in your kitchen and turns it into recipes. Tell me three things in your fridge or pantry and I'll make you three recipes with them." If they opened with a question like what to make tonight, answer it with this offer.
3. When they reply, add what they named with `add_pantry_items_bulk`. Two or five items are fine too. If they send a photo, read the items from it yourself instead of starting a scan. If they mention a diet or allergy, save it with `update_diet_profile` first so the recipes respect it.
4. Call `generate_recipe` once, with a prompt built around their items, such as "three dinners using chicken thighs, spinach and rice". That one call makes three recipes, with pictures, and saves all three to their recipe book. It uses one of their monthly ChefSense recipe generations. Tell them the recipes are on their way; it can take a minute or two.
5. Poll `list_recipes` until the three new recipes appear. For each, give the title, how long it takes and which of their items it uses. Offer to show one in full with `get_recipe`.
6. Say in a sentence what ChefSense did: their items and three recipes are saved in their ChefSense account, so they can come back to them in any chat.
7. Offer one more thing to try now: share a recipe link they love and get its shopping list, send a photo of a receipt or their fridge to see what to use first, or say what they eat or avoid so every recipe fits.

If `generate_recipe` says they've reached their limit, write three recipes yourself from the same items and offer to save the one they like with `save_recipe`.

ChefSense can't guarantee a recipe is safe for an allergy. If they mention one, remind them to check labels.

View saved version →

---
name: household-diets
description: Set up or update the diets, allergies and disliked ingredients of the user and the people they cook for in ChefSense. Use when the user mentions someone's diet, allergy or dislikes, or asks to update their household or diet profile.
---

Keep everyone's diet profile accurate, because every suggestion and recipe in ChefSense relies on it.

1. Call `get_household` to see who's in the household and their current diets and dislikes. Use `get_diet_profile` for the user's own profile.
2. Work out the change from what the user said, such as "Dana is vegetarian now and hates cilantro". If it's unclear who they mean or whether something is an allergy or just a dislike, ask.
3. Show the before and after for each person and ask before saving.
4. Save it:
   - **The user themselves:** `update_diet_profile` with `add_diets`, `remove_diets`, `add_dislikes` and `remove_dislikes`.
   - **Another household member:** `update_household_member` with a short `change_summary`. Diets and dislikes are **set**, not added to, so pass the complete new list: their current entries from `get_household` plus or minus the change.
5. Report what was saved. Anything ChefSense didn't recognise comes back in `skipped` or `warnings`. Tell the user and suggest the closest match.

You can update the user and the people they manage. Someone with their own ChefSense account in the household manages their own profile, so suggest they update it themselves. Diet and dislike changes can be reversed with `undo_last_change`; a whole `update_household_member` call is undone at once.

Allergies matter for safety. Record them, and remind the user that ChefSense can't guarantee a recipe is safe for an allergy and to check labels.

View saved version →

---
name: save-a-recipe
description: Save a recipe to the user's ChefSense recipe book from a link, a photo of a cookbook page or recipe card, or text in the conversation. Use when the user asks to save, keep or add a recipe to their recipe book.
---

Get a recipe into the user's ChefSense recipe book accurately, without duplicates.

1. Work out the source:
   - **A link:** fetch and read the page yourself, then call `save_recipe_from_url` with the `url` and the structured fields. If they already saved that link, ChefSense returns the existing recipe instead of a duplicate; tell them.
   - **A photo you can read:** read it yourself, then use `save_recipe`.
   - **The user wants ChefSense to read the photo:** use `start_recipe_scan`, poll `get_recipe_scan` until it's `draft_ready`, show the draft, and save it with `finalize_recipe_scan`, passing `edits` for anything they correct. Scans count toward their monthly ChefSense scans, so only do this when they ask for it.
   - **Text in the conversation**, including a recipe you wrote: use `save_recipe`.
2. Before saving, show the title, servings, ingredients and instructions you'll save. Ask about anything you couldn't read or that looks wrong.
3. Structure it:
   - Ingredients: one entry per ingredient with `name`, plus `quantity`, `unit` and `notes` (such as "finely chopped") where given.
   - Instructions: one string per step, in order. Call them instructions when you talk to the user.
   - Prep and cook time in minutes, if known.
   - A `source_hint` saying where it came from, such as "cookbook page".
4. Confirm it's saved and offer next steps: shop for it, or adapt it for someone in the household.

Saved recipes can be removed with `undo_last_change` straight afterwards.

View saved version →

---
name: set-up-my-diet
description: Save the diets, allergies and dislikes of someone who has just started using ChefSense, then suggest a dinner that fits. Use when a user new to ChefSense says what they eat, avoid or are allergic to.
---

The user found ChefSense moments ago and knows nothing about it yet. They've told you what they eat or avoid. Save it once, then show in the same reply that it works.

1. Save their diets, allergies and dislikes with `update_diet_profile`. Anything ChefSense doesn't recognise comes back in `skipped`; tell them and suggest the closest match.
2. If they mention other people they cook for, account for those people's needs in this conversation too. Don't ask them to set anything else up now.
3. Suggest one dinner that fits. Write it yourself, and say in a line how it fits each need they mentioned.
4. Say in a sentence what ChefSense did: it now knows what they eat, and every recipe it makes for them will respect that, in any chat.
5. Offer one more thing to try now: save this dinner to their ChefSense recipe book with `save_recipe`, or tell you three things in their fridge and ChefSense will make three recipes that fit their diet.

Diet changes can be reversed with `undo_last_change`. ChefSense can't guarantee a recipe is safe for an allergy, so remind them to check labels.

View saved version →

---
name: shop-for-a-recipe
description: Add the ingredients a recipe needs, minus what's already in the pantry, to the user's ChefSense shopping list. Use when the user asks what they need to buy for a recipe or to add a recipe's ingredients to their shopping list.
---

Turn a recipe into the shortest useful shopping list.

1. Find the recipe:
   - A saved recipe: find it with `search_recipes` or `list_recipes`, then `get_recipe`.
   - A recipe from the conversation or a page they shared: use its ingredient list as written.
2. Call `list_pantry` and `list_shopping_list`.
3. Sort the ingredients into three groups:
   - **Already have:** in the pantry in a large enough amount.
   - **Already on the list:** on the shopping list and not checked off.
   - **Need to buy:** everything else.

   Treat staples such as salt, pepper, oil and water as "already have" unless the pantry shows they've run out. If the amount in the pantry is unclear, put the item under "need to buy" and say so.
4. Show the three groups, scaled to the servings they want if that's different from the recipe.
5. Ask before adding the "need to buy" items with `add_shopping_list_items`, with quantities and units where the recipe gives them. Shopping list changes can't be undone.

ChefSense doesn't place orders; the shopping list is a list only.

View saved version →

---
name: stock-the-pantry
description: Add groceries to the user's ChefSense pantry from a list, a receipt photo or a shelf photo, and check bought items off their shopping list. Use when the user has been shopping or wants to add groceries, a receipt or a photo of their shelves to their pantry.
---

Get what the user just bought into their pantry with as little typing as possible.

1. Work out the source:
   - **A typed or spoken list:** use it directly.
   - **A photo you can read** (receipt or shelf): read the items yourself. Skip non-food lines, deposits, bags and totals. Expand receipt abbreviations where you're confident, and mark the ones you're unsure of.
   - **The user wants ChefSense to read the photo:** use `start_pantry_scan` (`kind: "receipt"` or `"shelf"`), poll `get_pantry_scan` every few seconds until it's `ready_for_review`, then show the detections. Scans count toward their monthly ChefSense scans, so only do this when they ask for it.
2. Show the items you'll add, with quantities, units and any expiry dates you can infer for fresh food. Ask before adding.
3. Add them:
   - Items you read or were given: `add_pantry_items_bulk`. Pass `confidence_hints` for items you weren't sure of, so they're flagged for review, and a short `source_hint` such as "receipt photo".
   - A ChefSense scan: `apply_pantry_scan`, with `reject_detection_ids` for anything the user didn't want.
4. Report what was added, merged into existing items, or skipped and why.
5. Call `list_shopping_list`. If any bought items are on it, offer to check them off with `check_shopping_list_items`.

Pantry changes can be undone with `undo_last_change`; shopping list changes can't.

View saved version →

---
name: weekly-dinners
description: Put together a week of dinners for the user's household from their ChefSense pantry and saved recipes, then add what's missing to their shopping list. Use when the user asks for dinners or meals for the week, or what to cook over the next few days.
---

Help the user decide what to cook for the next several days and get the shopping sorted.

1. Ask how many dinners they need and anything that changes the week, such as a busy night, guests or someone away. Skip this if they've already said.
2. Call `get_household`, `list_pantry` and `list_recipes`.
3. Propose one dinner per night in a short table: the day, the dish, and whether it's a saved recipe or a new idea. Plan around:
   - Every household member's diets, allergies and dislikes. Members with their own ChefSense account don't share their diet profile, so ask about them if it matters.
   - Using expiring pantry items early in the week.
   - Variety, so the same main ingredient doesn't repeat back to back.
   - Quick dishes on the nights they said were busy.
4. Let them swap dishes until they're happy.
5. Work out what to buy. For each saved recipe use `get_recipe`; for new ideas use your own ingredient list. Leave out anything already in the pantry in a large enough amount, and check `list_shopping_list` so nothing is added twice. Combine duplicates, such as onions needed by three dishes.
6. Show the list and ask before adding it with `add_shopping_list_items`. Shopping list changes can't be undone, so get a clear yes first.
7. Offer to save any new dishes they liked with `save_recipe`.

ChefSense can't guarantee a recipe is safe for an allergy, so remind them to check labels. ChefSense doesn't place orders; the shopping list is a list only.