Choose and order food with learned preferences, price comparison, and variety protection.
User wants their agent to handle the entire food ordering process — from deciding what to eat, through comparing options, to placing the actual order. Agent learns preferences over time and makes increasingly better choices.
Memory lives in ~/food-delivery/. See memory-template.md for setup.
~/food-delivery/
├── memory.md # Core preferences, restrictions, defaults
├── restaurants.md # Restaurant ratings, dishes, notes
├── orders.md # Recent orders for variety tracking
└── people.md # Household/group member preferences
User creates these files. Templates in memory-template.md.
| Topic | File |
|---|---|
| Memory setup |
memory-template.md| Decision framework | decisions.md |
| Ordering workflow | ordering.md |
| Common traps | traps.md |
All data stored in ~/food-delivery/. Create on first use:
mkdir -p ~/food-delivery
This skill handles:
User provides:
This skill NEVER modifies its own SKILL.md.
All learned data stored in ~/food-delivery/ files.
| User says | Store in memory.md |
|---|---|
| "I'm vegetarian" | restriction: vegetarian |
| "I love spicy food" | preference: spice_level=high |
| "Allergic to shellfish" | CRITICAL: shellfish (always filter) |
| "I don't like olives" | avoid: olives |
| "Budget around $20" | default_budget: $20 |
| "Usually order dinner around 7pm" | default_time: 19:00 |
CRITICAL (allergies, medical) → ALWAYS filter, never suggest
FIRM (religious, ethical, diet) → filter unless user overrides
PREFERENCE (taste) → consider but flexible
For CRITICAL restrictions:
When user asks to order food:
Step 1: Context
Step 2: Filter
Step 3: Compare
Step 4: Present
Step 5: Confirm & Order
Track in orders.md:
Triggers:
Before ordering:
Tell user: "Same order is $4 cheaper on [Platform] today"
When ordering for multiple people:
Default crowd-pleasers when no consensus:
| Context | Behavior |
|---|---|
| "I'm tired" | Comfort food, familiar favorites |
| "Celebrating" | Higher-end, special occasion spots |
| "In a hurry" | Fastest delivery, simple orders |
| "Working lunch" | Quick, not messy, productive-friendly |
| "Date night" | Quality over speed, ambiance matters |
| "Hungover" | Greasy comfort, hydrating, gentle |
| "Post-workout" | Protein-heavy, healthier options |
| Rainy day | Warn about longer delivery times |
| Friday night | Can wait for quality |
| Sunday morning | Brunch options, recovery mode |
When appropriate (not spammy):
Via browser automation:
Always confirm before final checkout.
If order has issues: