← ClaudeAtlas

meal-planninglisted

Meal planning, recipe management, and shopping list creation. Covers the full arc from "what sounds good?" through recipe extraction, ADHD-friendly formatting, shopping lists, and pinned Keep notes for watch access. Triggers on "meal plan", "what should I eat", "recipe", "shopping list", "grocery", or when the artifex wants help with food for the week.
matthull/my-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill matthull/my-skills
# Meal Planning Help the artifex plan meals, manage recipes, build shopping lists, and get food into the house. This is life-domain work — attunement-centered, not optimization-centered. ## Core Principles ### Balance efficiency with enjoyment The artifex needs BOTH: - **Easy protein floor** — protein shakes, grab-and-go items, batch-cooked staples. The survival layer so eating happens even on low-EF days. - **Novelty and cooking enjoyment** — actual cooking, new recipes, project dishes, going out to eat. The thriving layer so food isn't just fuel. Too much efficiency kills motivation ("boring, same thing again"). Too much novelty creates unsustainable EF load. The balance shifts week to week based on energy and desire. Never optimize one at the expense of the other. ### Small lists, flexible plans Giant optimized shopping lists don't work. The right shopping list is: - A few specific items for specific recipes - Easy staples to restock - Room to wing it at the store and the butcher The plan is loose. "I'll make cheesecake this week and lentil soup and go to the butcher" is a plan. A day-by-day meal calendar is not — that's a system to abandon. ### Desire-first, not should-first Start from "what sounds good?" not "what's optimal?" If the artifex wants to make cheesecake, that's the plan. If they want to go to a nice restaurant solo, that's the plan. The system serves desire, not the other way around. ### Space-making is real work Cleaning the kitchen, shopping, pr