jp/hermes-meal-suggestion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync: strict inventory-only rule for daily meals

Browse Source
This commit is contained in:
jp
2026-08-26 03:21:21 +01:00
parent c5f4fb1bc2
commit 9e448760cd
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
SKILL.md
View File

@ -82,8 +82,13 @@ Schema:
— these overlap heavily with the above, so a few smart picks (oily fish, eggs with — these overlap heavily with the above, so a few smart picks (oily fish, eggs with
yolk, greens, nuts/seeds) cover all three goals at once. Don't overcomplicate; note yolk, greens, nuts/seeds) cover all three goals at once. Don't overcomplicate; note
them as gentle "health boost" lines, not medical advice. them as gentle "health boost" lines, not medical advice.
- If the inventory is too sparse for a real meal, say so and list the top 2–3 - **STRICT inventory rule:** both daily meals MUST be built ONLY from items the user
things to buy. ACTUALLY HAS in `inventory.json` at the time. Never invent, assume, or add an
ingredient that isn't listed there. Recipe/web inspiration is fine, but only use
in-stock items — substitute with an in-stock item or drop the idea. Before sending,
cross-check every ingredient against inventory.json and remove anything not present.
If stock is too sparse for a real high-protein meal, say so and list the top 2–3
things to buy — do NOT fabricate meals from items you don't have.
## Email format ## Email format
Send via the helper (it reads SMTP creds from `~/.hermes/.env`): Send via the helper (it reads SMTP creds from `~/.hermes/.env`):