菜单
Walk the household through cooking hands-free, or capture a meal already made. Use for "I'm making the arroz caldo", "walk me through dinner", "let's cook" — and equally for "I made the chili last night", "we ate the leftovers". One flow owns the cooking log.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Plan meals — a week, a few days, tonight, or around a market haul. Use for "make me a menu", "what should we eat this week", "what's for dinner", "plan around what's in the fridge", and side questions like "what goes with the short ribs". Reads kitchen context, renders the interactive week card (the engine composes, the card presents and commits), rounds out plates, and reviews what needs buying.
Record what's physically in the kitchen. Use for "we're out of olive oil", "put 3 lb of beef in the freezer", "used the last of the parmesan", "picked up basil and tomatoes at the market". Merges instead of duplicating. A haul the household wants cooked from is a planning request.
File a bug to the maintainer when something is genuinely wrong — a failing action that can't be routed around, repeated corrections on the same point, or the member saying it's broken.
First-run setup, or reviewing what's saved. Use for "get me set up", "onboard me", "update my profile", "what do you know about me", or when the profile reads empty. Three areas and done — everything else is learned through use or managed in the app.
Flush the list — order online, walk a store, or hand off. Use for "place the order", "I'm headed to the store", "give me a shopping list", "shop it on Instacart", "I'm at Central Market". Capture is continuous; this flow is the deliberate flush, branch picked from the household's setup and this trip's words.
Internal shared rules for yamp, loaded by reference from the workflow skills (via their prerequisite line). Not invoked on its own.
| name | cook |
| description | Walk the household through cooking hands-free, or capture a meal already made. Use for "I'm making the arroz caldo", "walk me through dinner", "let's cook" — and equally for "I made the chili last night", "we ate the leftovers". One flow owns the cooking log. |
Prerequisite — if you haven't already this session, read the
yamp-coreskill before continuing.
Identify the dish: check read_meal_plan() first (a loose match to a planned dish counts — the plan has a soup and I say "made the soup"); otherwise a vibe-less search_recipes query lookup, or treat it as an off-cookbook meal.
Cooking now: pre-flight in chat, short turns — equipment the dish truly needs (against the profile's kitchen; gear I volunteer gets saved silently via update_pantry kitchen ops), the gather list, pin servings, and whether anything's short. Then display_recipe — its cook mode carries the steps, check-offs, and timers (I run timers, you never do); no card on this surface → a plain-text walk, one step per turn. Weave in a saved technique (read_guidance("cooking_techniques")) at the step where it applies, if one genuinely fits.
Capture — during the walk's finish, or a past-tense report: log_cooked — { type: "recipe", recipe, plan_row_id? } for a cookbook dish (its plan row clears itself), { type: "ad_hoc", name, protein?, cuisine? } otherwise; honest meal when known, past date when I said so. Ask what ran out ("did that finish the ginger?") → update_pantry removes. Then one light ask: favorite it, or a note for next time? (set_recipe_disposition / add_recipe_note.) Don't propose a new menu unless I ask.
