Recipe Collector

Send a recipe

Hey Babe, try this one.

Got a dinner that deserves a spot on the board? Email it to the taste testers. If it makes the cut, it gets dealt into somebody’s week.

tastetest@heybabewhatsoundsgood.com

Paste it into Gmail, or whatever you use, and hit send.

What to send

Every email gets read. No promises on the ones with raisins.

Go pro

Make the list fill your cart.

Build your own copy and your shopping list goes straight into your grocery delivery cart. Kroger stores (King Soopers, Ralphs, Fred Meyer, Smith’s and more) have a free developer API, so the whole week shops itself. Anywhere else, the list still copies and prints.

All it takes

  • A coding agent. Claude Code or Codex. It runs on your computer and does the building.
  • Your own keys. An Anthropic or OpenAI API key for importing recipes and drawing the cards, a few cents a recipe, plus a free Kroger developer key for the cart.

Paste the prompt below into the agent, fill in your zip code and store when it asks, and let it cook.

The build prompt

Build me a personal recipe app called Recipe Collector. I want to run it on my own computer and open it from a tablet or phone on my home Wi-Fi. Ask me anything you need before you start, then build it step by step and tell me how to run it.

What it does:
1. Recipes are markdown files in data/recipes/, one per dish, with frontmatter: title, cuisine, category, totalTime (minutes), serves, weather (cozy | cool | any), motif, source, blurb, tags, image. The body has "## Ingredients" (a list, with optional bold "For the sauce" group lines) and "## Instructions" (a numbered list). No database.
2. Adding recipes: I can photograph a recipe, upload a PDF, or paste a link, and an AI model turns it into one of those markdown files. Rewrite the instructions in your own words and keep the source link, so the files are mine to share.
3. Card pictures: ever
← Back to this week
What's on the menu
1
2
3
4
5
6
7