🍳 funcooker

readme

a family food system: recipe library, lean stock, derived meal schedule

Spec: ROADMAP.md

quickstart

bin/setup --skip-server
LLM_MODEL=<model id> bin/dev

library

Every record the app shows can be created, edited and deleted.

recipe import

/recipe_imports/new takes a URL, pasted text, photos of a cookbook's pages, or the name of a dish. The import runs as a background job and its page refreshes onto the new component when it is done.

Each import makes one Component: its steps in order, and its ingredient lines as {amount, unit, ingredient, note}. From (a book and page, say) is kept on the component and shown on its page, and can be edited there.

Amounts are stored for one adult. The model reports how many adult servings the source makes — from its yield, estimated when the yield is in pieces ("24 cookies") or missing — and each amount is divided by that, to 4 decimal places. Amounts written inside step text are not scaled. Ingredients are matched to an existing Ingredient by lowercase name, or created.

A page that answers an error, a model that cannot be reached or runs out of tokens, a source with no ingredients and no steps, and a serving count that is not above 0 each fail the import, with the reason on its page. Photos that yield no recipe, and a server that refuses images, say what is needed: a vision-capable model loaded in llama-swap with its --mmproj file, and LLM_VISION_MODEL set to its id.

schedule

/schedule shows the meal up next with Cook, Served, Skip and I'm tired, how many easy meals the freezer bank holds, a plan form, and the meals from a week back to four weeks ahead.

Plan fills the chosen meals (breakfast, lunch, dinner) over the chosen days, one slot at a time in date order, for everyone who eats by default. Dishes that any of them is restricted from are never candidates. The rest are scored, and the highest wins; ties go to the dish name.

Skip marks the meal skipped and derives every planned meal after it again, from the stock and dates as they are now. I'm tired marks the meal swapped and puts in its place, for the same people, the frozen dish that expires soonest that none of them is restricted from. A lot counted in servings must have enough for them. A meal from the freezer shows Reheat in place of Cook.

Served on a meal whose dish is in stock whole (a frozen dish, say) draws its servings from stock. On any other meal it only marks the meal served.

Each meal lists who is eating it and the servings that makes: the sum of their portions. A new meal starts with everyone who eats by default; tick anyone else in on the meals they come to. A dish anyone at the meal is restricted from is refused, naming them. There is no override: a restriction is something they do not eat. One meal per slot.

shelf life

A component has two shelf lives, both in days: how long it keeps once made, which sets the expiry of prepped stock, and how long it keeps frozen, which sets the expiry of freezer stock. A freezer life of 0 means it does not freeze well (a dressed salad, mayonnaise), and it cannot go in the freezer.

The model estimates both in one call, conservatively and from food-safety guidance, for each imported recipe and each component Decompose creates, and on Estimate shelf life (one component) or Estimate missing shelf lives (every component missing either). Only a blank one is filled in, except with Estimate again, which replaces both. The component page shows the days and where they came from; the components list shows both. Setting either by hand replaces its estimate. An answer that is not a whole number of days (above 0 for the fridge, 0 or above for the freezer) is not stored.

cook

/cook lists cooking sessions. Both kinds are walked the same way: one step at a time in large type, with that step's ingredients scaled to the servings (a step that names none shows the whole component's, on its first step). Done moves on. A passive step with a time has Start: it moves to the countdown strip at the top, which stacks, and is marked done from there. Any step can be undone.

The prep planner looks at the meals planned over the next days (7 by default) and suggests every component inside their dishes that has steps, for the servings those meals need less the prepped and frozen servings in stock. A meal whose dish is in stock whole needs nothing. Each can be unticked, its servings changed, or some of them set aside to freeze (Of which, freeze: cook once, freeze half), and any other component added. A component that does not freeze well cannot be set aside.

The model orders a prep session's steps: long passive steps as early as they can go, long components first, one active step at a time, grouped by technique or station. Each component's steps are then put back in their recipe order within the places they got, and any step it dropped is appended. If the model cannot be reached, the session says why and can be cooked in recipe order instead.

Stock is drawn soonest-expiring first, and only from lots in the unit the recipe measures in. What could not be drawn (none in stock, a different unit, or too little) is listed on the finished session rather than guessed.

prep blocks

The prep planner also says when: how long the suggested prep takes, the first meal that needs it, and the first free stretch each day long enough, each with Book. Booking takes the ticked components as they are in the form and makes a prep block, listed under booked prep on /cook and put on the Mac's Calendar.

The calendar is read through the Mac's Calendar, so every calendar added to it counts (iCloud, Google, Exchange), recurring events included and events marked free left out. lib/calendar/calendar.js does the reading and writing through EventKit:

A prep block's event carries its components, servings and time estimate, and a link back to the block. The app knows its events by a line at the end of their notes (funcooker prep block <id>): it moves them rather than adding them again, and removes any whose block is gone. The first run asks macOS for full access to Calendars.

household

/household lists who eats.

Each member's page adds, edits and removes their food needs: an ingredient, a family or a component, as a restriction (never planned when they are eating) or a preference that they like or dislike (scored).

Below them, the household's settings:

decompose

A component's page has Decompose while it is not yet made of other components. The model breaks the recipe into the parts worth making on their own (a sauce, a marinade, cooked rice, a dough) and rewrites it to use them, in a background job.

The model judges the recipe before breaking it up:

A borderline plan is only applied to the recipe as it was judged; one edited since has to be decomposed again. The recipe's ingredients and steps as they were are kept on the Decomposition. A component and anything it is part of are never offered for reuse inside it. If the model finds nothing to break out, or names a component that does not exist, nothing changes and the reason is shown.

receipts

/receipts/new takes a photo of a grocery receipt (JPEG, PNG or WebP) or its text, pasted. The model reads it in a background job into lines, and the receipt's page refreshes onto them.

Totals, tax, payments, discounts, coupons, deposits and bag fees are left out.

Every line is editable before anything is stocked: whether it is included, its ingredient, quantity, unit and keep-until date. An ingredient not yet in the library is marked new. Stock these makes one raw StockItem lot per included line, recorded as a receipt transaction, and creates any new ingredients. An included line needs an ingredient and a quantity above 0. A receipt is stocked once.

A photo the model cannot read fails the receipt with the model's name, the server's error, and what is needed: a vision-capable model loaded in llama-swap with its --mmproj file, and LLM_VISION_MODEL set to its id. A photo that yields no items says the same. Pasted text needs neither.

stock

/stock lists every lot on hand, soonest to expire first.

freezer bank

Frozen stock is component stock like prepped stock, only kept in the freezer and for longer. A frozen component counts wherever a prepped one does: the planner's stock score, the prep planner, the shopping list and cooking all draw on it. A frozen dish is an easy meal, the backup plan behind I'm tired.

/freezer shows:

Both take any number of servings up to the lot's, and are recorded as freezer transactions on both lots. Freezer stock can also be added by hand from /stock.

thaw reminders

Meals are taken in date order, as cooking takes them. A dish, or a component inside it, comes from stock when its prepped and frozen servings together cover the meal; otherwise it is cooked, and the components inside it are taken the same way. The fridge is used first. What it is short of is a thaw, from the freezer lot that expires soonest, due the evening before the meal (or now, for a meal today). Thawing it moves it to the fridge, and it drops off the list.

A reminder is titled with the component, the servings and the day ("Thaw salsa verde, 1.5 servings, for Thursday"); one already on the list and not ticked is skipped, so sending again adds only what is new.

shopping

/shopping lists what to buy for the meals planned over the next days (7 by default, up to 28): everything they need, scaled to each meal's servings, less what is on hand.

Each item's notes say which meals it is for, and what is needed and on hand.

To get it into Reminders:

The Shortcut, built once in the Shortcuts app:

1. Get Contents of URL: https://<host>/shopping.json
2. Get Dictionary Value for items
3. Repeat with Each item:
   1. Get Dictionary Value for title in Repeat Item
   2. Find Reminders where List is Groceries, Title is the value, and Is Not Completed
   3. If Reminders has no value: Add New Reminder with the title, in Groceries, with Notes from notes

Run again, it only adds what is not already on the list.

The first send asks macOS for access to Reminders. A refusal fails the send with where to allow it: System Settings → Privacy & Security → Reminders, and Automation for the process running the app.

configuration

Each request asks for temperature: 0, a json_schema response format, and chat_template_kwargs: {enable_thinking: false}, and waits up to 600 seconds for the reply. A photo is sent inline as a base64 image_url part.

To list the model ids, from a machine on the tailnet:

curl -s https://chat.bobbymeyer.com/v1/models | jq -r '.data[].id'

tech

• Rails 8.1, Ruby 3.3.6, SQLite
• UI: its-swiss v1.0.0
• Tests: bin/rails test, HTTP stubbed with WebMock
• Lint: bin/rubocop