From grimoire
Creates structured, balanced menus for restaurants, catering, households, or institutions, aligning nutrition, operations, and guest experience.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:design-menu-planningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a structured, balanced menu — for home, restaurant, or institution — that aligns nutritional goals, operational capacity, ingredient availability, and guest experience.
Create a structured, balanced menu — for home, restaurant, or institution — that aligns nutritional goals, operational capacity, ingredient availability, and guest experience.
Adopted by: Culinary Institute of America (CIA), National Restaurant Association Educational Foundation, Academy of Nutrition and Dietetics, school nutrition programs (USDA NSLP), hospital food service, and all accredited food service management programs. Impact: Restaurants with structured menu planning achieve 20-30% lower food cost than those without; school nutrition programs using cycle menus reduce food waste by ~35% (USDA FNS data); hospital menus designed by registered dietitians reduce patient length of stay by 0.5-1.2 days in studies measuring nutrition-sensitive outcomes; Cornell University research found menu structure and sequence influence caloric selection by 15-20%. Why best: A menu is not a list of dishes — it is a system that determines purchasing, labor, equipment, food cost, nutritional adequacy, and guest satisfaction simultaneously. Planning it systematically ensures all these factors are balanced before service begins, not discovered through costly in-service failures.
Sources: CIA "The Professional Chef" 9th ed., Chapter 2; NRA Educational Foundation "MenuLogic" planning framework; AND Evidence Analysis Library, Menu Planning (2021); USDA NSLP Meal Pattern Requirements (2023).
Define the menu context and constraints — Identify: audience (age, dietary restrictions, cultural context), service type (à la carte, fixed-price, buffet, institutional cycle), budget per person, equipment available, staff skill level, and any regulatory requirements (USDA school meal patterns, hospital therapeutic diet protocols).
Establish nutritional parameters — For institutional and healthcare menus: use USDA MyPlate or therapeutic diet standards (renal, diabetic, cardiac) as the framework. For restaurant menus: ensure the overall menu offers nutritionally diverse options even if individual dishes are indulgent. Document the target macronutrient and micronutrient goals per meal or day.
Determine the menu structure — Choose the organizational framework: traditional (appetizer/entrée/dessert), tasting menu (6-10 courses), cycle menu (rotating set over 4-6 weeks), prix fixe, or à la carte. The structure determines how many dishes are needed and how they relate to each other.
Build the protein anchor for each meal — For each meal position, select the protein anchor first. Proteins drive food cost, cooking method, and equipment use. Ensure variety across the week or menu: poultry, red meat, fish, legumes, eggs. No more than two meals in a row should share the same protein category.
Pair grains, starches, and vegetables — For each protein anchor, select complementary carbohydrate and vegetable pairings that: share no cooking equipment conflict, contrast in color and texture, and support the nutritional target. Classic pairings: lean protein + whole grain + bright vegetable; rich protein + acidic vegetable + neutral starch.
Balance flavors across the menu — A well-planned menu does not repeat the same flavor profiles consecutively. Map each dish on a scale of: richness (light to heavy), acidity (bright to muted), spice level (mild to bold), and cooking method (roasted, braised, raw, fried). Adjacent courses or consecutive days should contrast.
Calculate food cost for each item — For each dish, calculate the food cost percentage: (ingredient cost ÷ selling price) × 100. Target 28-35% for restaurant menus. Items above 35% require repricing or portion adjustment; items below 20% may be underportioned or low-value. For institutional menus, cost per meal must align with reimbursement rates or budget allocations.
Evaluate equipment and labor load — Map each dish to the equipment and skilled labor it requires. A menu where every dish requires the grill station at the same time creates service failure. Distribute dishes across oven, sauté, grill, and cold prep stations. Similarly, distribute labor-intensive prep across the week for institutional menus.
Plan for ingredient cross-utilization — Identify ingredients that appear in multiple dishes. Cross-utilization reduces purchasing complexity and waste. Example: roasted chicken serves as entrée on Monday, in a grain bowl on Tuesday, in a soup on Wednesday. This is menu engineering, not repetition.
Test, collect feedback, and revise — Run the menu for a defined trial period (2 weeks for institutions; a full service cycle for restaurants). Track: which items sell fastest, which are returned, food cost actuals vs. projections, and any complaints about nutritional balance or variety. Revise based on data, not assumption.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireBuilds a weekly meal preparation system for batch cooking, portioning, and storing meals to reduce daily cooking time while maintaining nutrition.
Teaches cooking through culinary principles, food science, and flavor architecture. Covers technique, troubleshooting, menu planning, and cultural cuisine.
Applies dietetic communication best practices for client education, meal planning, behavior change counseling, and health literacy adaptation.