Claude plans meals well and counts nutrients badly. Give it four things - who is eating, what each night of your week actually looks like, the foods your household refuses, and what is already in the fridge - and it will hand back a seven-day plan, a prep session and one consolidated shopping list in about two minutes. What it cannot do is produce reliable calorie or macro totals, know about a current recall, or read the allergen label on the packet in your hand. Plan with it; verify the numbers and the safety elsewhere.
What do you have to tell Claude before it can plan anything?
A bare "plan my week" gets you a magazine plan: seven ambitious dinners for a household that does not exist. Six inputs do almost all the work, and they take one paragraph to write:
- Headcount and appetites. "Two adults and a 7-year-old" produces different portions than "two adults".
- The shape of the week. Which nights you walk in at 19:30, which night you can actually cook, which nights someone is out.
- Hard nos. Allergies, intolerances, and the things nobody in the house will eat. State them once, at the top.
- Equipment. One oven, a hob, a slow cooker. Otherwise it will plan three dishes that all need the oven at 200°C at 18:45.
- What is already in the house. Half a cabbage, a bag of lentils, three chicken thighs. This is where the savings live.
- Where you shop. Supermarket and whether it is one delivery or a walk-round.
Here is the whole thing as one prompt. Replace the bracketed parts and paste it in:
Rule 5 matters. Left to itself Claude will decorate every dish with a confident calorie count that is a guess about portion weight multiplied by a half-remembered nutrient value. Telling it not to keeps the plan honest. Rule 4 matters for the same reason people abandon plans: forty minutes of simmering while you do something else is not the same as forty minutes of chopping.
How do you turn that into a prep session worth doing?
Most weeknight pain is repeated work: the same onion diced five times, the same grain boiled five times. A prep session collapses that into one block. The trick is to make Claude schedule the equipment, not just list the tasks.
That last instruction is the one that earns its place. Ask for it and you get told that dressed salad, sliced avocado and anything breaded is a Sunday mistake - which is the kind of thing a plan quietly gets wrong until you have thrown away three lunches. If baking is part of your prep block, our baking assistant guide covers the parts where precision actually matters.
Need one dinner solved tonight rather than a whole week planned? This prompt pack takes mixed dietary requirements for a single meal without the planning session.
View AI Meal Generator →How do you get one shopping list instead of five trips?
The plan is worthless if it produces a list in recipe units. Recipes say "150g crème fraîche"; the shop sells a 300g tub. Ask for supermarket units and the aisle order you actually walk in:
The "do not estimate prices" line is not optional. Claude does not know what your supermarket charged this week and will produce a plausible total anyway. If you want the pantry side handled properly - what you actually have, what is about to turn - that is the job in our grocery and pantry manager guide.
Where does Claude get food wrong?
This is the section worth reading twice, because the failures are the confident kind.
- Nutrition arithmetic. Calorie and macro figures come out fluent and precise and are estimates stacked on estimates - a guessed portion weight against a remembered nutrient value. If the numbers matter, look the food up in the USDA's free FoodData Central database or scan the barcode in a tracking app instead.
- Anything clinical. Claude is not a dietitian, a doctor or a diagnosis. If anyone eating is on a therapeutic diet, managing diabetes, kidney disease, coeliac disease or an eating disorder, is pregnant, or has a diagnosed allergy, the plan needs a qualified professional's eyes on it before it becomes your week. Use Claude for the logistics; leave the medical decisions to a human who can see the whole picture.
- Recalls and labels. Training data has a cutoff and manufacturers reformulate constantly. Claude cannot tell you whether the jar in your hand contains sesame this month, or whether a batch has been recalled. Read the physical label, every time, for every allergen.
- Yields. "Serves 4" is a guess about your family's appetite. Expect to correct it after week one, then tell the skill what the real portion was.
- Your oven. Times are for a generic oven. Yours runs hot or cold and it does not know that.
Food safety is on you as well, and batch cooking sits right on top of the rules. The USDA's guidance is the reference, not the chat window: cooked leftovers keep 3-4 days in the fridge or 3-4 months in the freezer, perishable food should be refrigerated within two hours of cooking (one hour if the room is above 90°F/32°C), and 40-140°F (4-60°C) is the range where bacteria multiply fastest. That is why you divide hot food into shallow containers rather than putting a whole stockpot in the fridge.
How do you install the skill so it stays loaded?
A KissMySkills skill is a ZIP file with a SKILL.md at its root. In the Claude desktop app, open Customize → Skills, add a skill, upload the ZIP, and toggle it on. Uploading your own skills is a paid-plan feature - Pro, Max, Team or Enterprise - with code execution enabled (checked August 2026).
If you are on the free plan, or you work in ChatGPT or Gemini instead, the fallback is straightforward: open the SKILL.md in any text editor and paste its contents into custom instructions - a Claude Project's instructions, a ChatGPT custom GPT, or a Gemini Gem. Same behaviour, you just re-paste it for each new workspace.
For eating goals rather than logistics - portion structure, protein targets, building meals around training. Still general guidance, not clinical advice: a dietitian is the professional for a medical diet.
View Freya →Why keep a loaded skill instead of re-pasting a prompt?
Because the second week should be cheaper than the first. A loaded skill already holds the headcount, the equipment, the hard nos and - if you tell it - which dishes landed and which got scraped into the bin. That turns Sunday from a briefing into one sentence: "same as last week but Thursday is now a late one and nobody wants the lentil thing again."
In summary:
For a weekly plan, a prep session and one shopping list, use Paolo - Meal Planner & Prep AI Skill ($14.99). For eating goals on top of the logistics, add Freya ($14.99). For one dinner tonight, the AI Meal Generator ($9) is enough. None of them replace a dietitian, and none of them read the allergen label for you.
Paolo - Meal Planner & Prep AI Skill
Plans to the week you actually have, designs the prep session around your oven, and outputs one shopping list in supermarket pack sizes. Works with Claude, ChatGPT, or any AI chat.
KissMySkills is a marketplace of 853 AI skills, 158 prompt packs, 55 agents & free tools for Claude, ChatGPT & any AI chat. 30-day money-back guarantee.
Related Skill Guides
- How to Use Claude as a Recipe Creator (and Why You Still Need a Thermometer)
- How to Use Claude as a Baking Assistant: The Elise Skill Guide
- How to Use Claude as a Wine & Drinks Advisor: The Henri Skill Guide
- How to Use Claude as a Nutrition Coach (and Why Its Calorie Numbers Are Guesses)
- How to Use Claude as a Fitness & Wellness Planner: The Petra Skill Guide
- How to Use Claude as a Grocery & Pantry Manager: The Margot Skill Guide
- How to Use Claude as a Home Organiser: The Astrid Skill Guide
- How to Use Claude as a Garden Planner: The Ruben Skill Guide
- How to Use Claude for DIY & Home Improvement: The Lars Skill Guide
- How to Use Claude as an Interior Design Advisor: The Stella Skill Guide