meals-agent
CLAUDE.md0 starsChanged 8 months agoMITView on GitHub
Personal meal planning system for a family. User-specific constraints (diet, excluded ingredients, stores, thresholds) live in data/config.yaml. All skills read this file at startup. See samples/config.sample.yaml for the format and defaults. If data/config.yaml is missing, run /meal-setup to create it.
In this repository5 other files it gives its agents.
- meal-addSkill
- meal-flyerSkill
- meal-planSkill
- meal-receiptSkill
- meal-setupSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
All skills read this file at startup.
- Very specific: line 10
If data/config.yaml is missing, run /meal-setup to create it.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meal OS
Personal meal planning system for a family.
Household Configuration
User-specific constraints (diet, excluded ingredients, stores, thresholds) live in data/config.yaml.
All skills read this file at startup. See samples/config.sample.yaml for the format and defaults.
If data/config.yaml is missing, run /meal-setup to create it.
Directory Structure
data/ — local household data (gitignored)
- data/config.yaml — household preferences: diet, stores, excluded ingredients, thresholds
- data/recipes/ — one markdown file per recipe (from /meal-add)
- data/canonical-ingredients.yaml — authoritative ingredient normalization reference
- data/flyers/ — parsed weekly store flyers (from /meal-flyer)
- data/meal-plans/ — weekly meal plans (from /meal-plan)
- data/shopping-lists/ — aisle-grouped shopping lists (from /meal-plan)
- data/receipts/ — receipt images, price history ledger, and OCR aliases (from /meal-receipt)
samples/ — sanitized examples (tracked in git)
- samples/flyers/, samples/meal-plans/, samples/shopping-lists/, samples/receipts/
Skills
- /meal-add — recipe intake and normalization
- /meal-flyer — store flyer parsing + loss leader detection
- /meal-plan — weekly meal planning + shopping list generation
- /meal-receipt — receipt OCR, price tracking, and alias learning
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

