
You've probably done this: asked ChatGPT for a meal plan, got something that looked reasonable, maybe even saved it — and then cooked exactly zero meals from it by Thursday.
The plan wasn't wrong exactly. It just didn't fit your Tuesday. Or your fridge. Or the fact that "30-minute chicken" assumes a level of mise en place you don't have at 7pm after a full day.
The fix isn't a better AI. It's a better prompt. Specific constraints produce specific output. Vague requests produce plans that belong to no one in particular.
This is a prompt library organized by situation. Each one is ready to copy and paste — swap the brackets for your details and you're done. No tutorial, no preamble. Just prompts that are structured to get output you'll actually use, and follow-up fixes for when the first draft misses.

ChatGPT generates from what you give it. A prompt with no constraints — "give me a weekly meal plan" — forces the model to fill in every blank with assumptions: two adults, moderate cooking skill, no restrictions, 45 minutes available each night, no budget ceiling. Those assumptions are wrong for most people most of the time, which is why the output feels like it was written for someone else.
The prompts below front-load the context that changes the output most: household size, schedule, restrictions, and goals. That's the structural fix.
"Healthy meals" and "easy dinners" are goals ChatGPT can't operationalize without more input. Healthy by what standard? Easy relative to what cooking skill? The model defaults to middle-of-the-road interpretations that satisfy no one in particular.
Replacing vague goals with specific constraints — "high protein, no pork, under 30 minutes on weeknights" — produces output that's actually calibrated to your situation. Every prompt below includes a constraints block for exactly this reason.

Best for: Households of 3 or more, mixed preferences, need variety without a different complex recipe every night.
Plan 5 weeknight dinners for a family of [number], including [ages of children
if relevant, e.g. "two kids aged 6 and 9"].
Constraints:
- Weeknight cook time: max [X] minutes including prep
- At least 2 meals must be kid-friendly (no strong spices, familiar ingredients)
- Proteins to include across the week: [e.g. chicken, beef, one meatless]
- Foods to avoid: [list allergies or strong dislikes]
- I want at least one meal that makes enough for next-day lunch leftovers
For each dinner: list ingredients, estimated cook time, and one note on
what kids can help with if anything.
Why it works: the kid-friendly constraint and leftover flag produce structurally different output than a generic family dinner request. The "what kids can help with" line is optional — remove it if irrelevant, keep it if you want lower resistance at the dinner table.
Best for: Keeping weekly grocery spend predictable without giving up variety.
Create a 5-day dinner plan for [number] people with a grocery budget of
approximately $[amount] for the week.
Rules:
- Prioritize ingredients that appear in more than one meal (reduce waste)
- Protein sources should be cost-effective: chicken thighs, eggs, canned beans,
or ground meat preferred over premium cuts
- No ingredients I'd only use once and have to throw away the rest
- Dietary restrictions: [list or "none"]
- Cooking skill: [beginner / comfortable home cook]
At the end, list the groceries I need grouped by category.
Flag which items are used in multiple meals.
Why it works: the "appears in more than one meal" rule is the most important line in a budget prompt. Without it, AI generates five unrelated meals with five unrelated shopping lists. With it, you get a plan built around ingredient overlap — which is how budget cooking actually works.
Best for: Anyone building around a protein target, training or not, who wants prep-friendly meals that aren't the same chicken-and-rice every day.
Create a 5-day meal prep plan targeting [X]g of protein per day, for one person.
Prep sessions: [Sunday only / Sunday + Wednesday]
Total prep time per session: max [X] hours
Storage: [fridge only / fridge + freezer]
Dietary restrictions: [list or "none"]
Protein sources I'm willing to eat: [e.g. chicken, beef, eggs, Greek yogurt,
lentils — list what you'll actually use]
Protein sources to avoid: [list or "none"]
For each meal: protein content, prep instructions, storage life, and
how to vary it across the week so I'm not eating the identical thing 5 days in a row.
Why it works: the "vary it across the week" instruction is what separates this from a standard meal prep prompt. Without it, AI gives you one recipe scaled up. With it, you get a base prep (e.g. cooked chicken) with four different ways to use it — which is how real meal prep works for people who get bored easily.
Best for: Anyone new to cooking who wants simple meals with minimal equipment and clear explanations, not just ingredient lists.
Suggest 4 simple dinners for someone who is new to cooking.
Rules:
- Maximum 6 ingredients per meal (not counting salt, pepper, oil)
- No equipment beyond a pan, pot, and oven
- No techniques that require timing precision (no deep frying, no temperature probes)
- Each meal should take under 30 minutes
- Dietary restrictions: [list or "none"]
For each meal:
1. Ingredient list with quantities
2. Steps written for someone who has never cooked this before
3. What "done" looks, smells, or feels like — not just a timer
4. The one most common mistake and how to avoid it
Why it works: the "what done looks like" and "most common mistake" instructions extract information that standard recipe formatting never includes. For beginners, this is the difference between a recipe that works the first time and one that requires three failed attempts to calibrate.
If your first output has unrealistic timing or repeats the same protein three nights in a row, send a follow-up rather than starting over:
The plan you generated has two problems:
1. Several meals list 20-minute cook times that would realistically take 35-40 minutes.
Revise the plan so that weeknight meals are genuinely under [X] minutes,
not optimistically under [X] minutes.
2. [Protein] appears on [days]. Replace one of those with a different protein.
Keep everything else the same.
The "keep everything else the same" instruction matters. Without it, ChatGPT often regenerates the entire plan rather than making the specific fix you asked for.
If your output is a list of five unrelated recipes with no structural logic, this follow-up prompt adds coordination:
Revise this meal plan to:
1. Identify which meals can share grocery list ingredients — adjust recipes
where needed to create overlap without changing the meal type
2. Flag any meal that produces leftovers usable for next-day lunch
3. Generate a consolidated grocery list grouped by: produce, protein, dairy,
pantry/dry goods, other. Mark items used in more than one meal with an asterisk.
This prompt works on any meal plan output — paste the plan in and follow with this request. The grocery consolidation step alone typically reduces a shopping list by 20-30% in item count.
Solo meal planning has a specific problem: most AI-generated plans are implicitly designed for two or more people, which means portion sizes, ingredient quantities, and batch cooking logic are all wrong by default.
Add this line to any prompt: "This is for one person. Quantities should reflect single-serving portions, and flag any recipe where halving the ingredients changes the cooking method or timing."
The second part of that instruction catches the cases where batch cooking logic breaks down at single-serving scale — e.g. roasting half a sweet potato behaves differently than roasting a full one.
Family meal planning fails most often on preference collision — one person's dietary restriction or strong dislike forces the whole household into a narrower recipe set than feels fair. The fix is explicit in your prompt:
Add: "The plan must work for everyone with these restrictions: [list]. Separately, [person] dislikes [specific foods] — avoid these in their portion specifically, or suggest a simple swap so everyone can eat the same base meal."
The "simple swap" framing is better than asking for completely different meals per person, which creates more cooking work, not less.

For 4-day work weeks, irregular schedules, or weeks where cooking time is genuinely variable:
My cooking availability this week is uneven:
- Monday: 20 minutes max
- Tuesday: 35 minutes
- Wednesday: no cooking (use leftovers or something no-cook)
- Thursday: 45 minutes available
- Friday: 20 minutes max
Build a dinner plan that matches this schedule exactly.
Don't assign involved recipes to short-time nights.
Mapping meals to actual available time — rather than averaging across the week — is the single most effective change for people whose plans consistently collapse mid-week.
Building the plan is the easy part. The harder part is carrying it forward — knowing what you cooked, what worked, and adjusting next week without starting from scratch every Sunday. At Macaron, you can track your meal plans, log what you actually made, and build a system that gets better week over week.

What's the difference between this and the ChatGPT meal plan prompts guide? The ChatGPT meal plan prompts guide covers four core prompt templates (weekly dinner, calorie-aware, meal prep, budget) with an explanation of how to build the input. This page is a prompt library organized by situation — more templates, less explanation, faster to use if you already know the basics.
How do I get ChatGPT to stop repeating the same meals every week? Add an explicit variety constraint: "Do not use the same protein source more than twice in a 7-day plan. Include at least one meatless dinner." Without this instruction, AI defaults to a narrow rotation. The constraint forces it out of that pattern.
Can I use these prompts with Claude or Gemini instead of ChatGPT? Yes. These prompts are structured around constraint-based input, which works across all major LLMs. The output quality varies slightly between models but the prompt structure transfers directly.
How long should a meal planning prompt be? Long enough to cover: household size, time available each night, dietary restrictions, budget (if relevant), and any variety rules you care about. That's typically 6-10 lines. Shorter than that and the model fills in blanks with assumptions. Longer than that and you're over-specifying in ways that constrain the output unnecessarily.
What do I do if the grocery list is too expensive? Follow up with: "The grocery list for this plan would exceed my budget. Suggest three ingredient substitutions that reduce cost without changing the meal type. For each substitution, explain what changes in the dish." This targeted follow-up works better than asking for a completely new plan.
Related Articles