← ClaudeAtlas

weekly-meal-plannerlisted

Plan a week of meals around the staples someone already keeps on hand. Produces an editable N-day plan (default 5 cooking nights + 2 flex days for leftovers or eating out), a grocery list grouped by store section, prep/cook notes with thaw/make-ahead timing, and short recipes. Optionally estimates per-plate calories and macros for a "primary eater" when targets are provided. Accepts a photo of your fridge, pantry, or grocery receipt in place of typing what's on hand. Use when the user wants to map out weekly meals, build a meal plan, plan dinners for the week, or organize a grocery run. Reads a preferences file if present; otherwise asks a few short questions first.
marklavine-mlv/weekly-meal-planner · ★ 2 · Data & Documents · score 75
Install: claude install-skill marklavine-mlv/weekly-meal-planner
# Weekly Meal Planner Turn a household's staples and a week's constraints into a concrete, cookable plan. The output is meant to be *edited* — treat every plan as a first draft the user will push back on (especially on portions and counts). ## 0. Load context before planning 1. **Look for a preferences file.** Check the conversation/project for `preferences.md` (or ask the user to paste theirs). It defines household size, meals to plan, dietary rules, staples, stores, and optional macro targets. The template is `preferences.example.md` in this skill. 2. **If no preferences exist, ask a short intake** — keep it to **5 questions in one message**, and fill sensible defaults for anything they skip (say which defaults you used): - Who's eating? (# adults, # kids; is it one batch for the whole table?) - What staples/proteins do you want to build around this week? Anything already on hand? *(You can snap a photo of your fridge, pantry, or grocery receipt instead of typing.)* - Any allergies, dislikes, or "never serve" foods? - How many cooking nights, and how many flex days for leftovers/eating out? *(default: 5 + 2)* - Want per-plate calories/macros? If so, for whom, the targets, and is each macro a **floor to hit** (e.g. protein) or a **ceiling to stay under** (e.g. fat)? Default silently on the rest (dinners only; ask store/meal-scope later only if it matters). 3. **Ask what's already in the house** if they didn't say. Plans should *use