Remy
A notebook for cooks who think in pairings — dishes, ingredients, combinations.
- Year
- 2026
- Status
- In progress
- Stack
- Figma, Next.js, Postgres, Anthropic Claude
- Code
- GitHub →
Wireframes and interactive screens.
The premise
There's a scene in Ratatouille where Remy eats a strawberry, then a piece of cheese, then both at once — and you watch his brain light up. That's the unit of cooking I care about. Not the recipe; the pairing. The thing that makes a thing.
Remy is a notebook for that. It lets you pin dishes you love, ingredients you keep coming back to, and the combinations that worked the last time. Then it helps you build the next meal out of what you already trust.
How it works
The data model is three nouns — Dish, Ingredient, Pairing — and a few verbs: pin, combine, vary. Each pin carries a small note (a flavor, a texture, a temperature). Pairings are pins of pins. The graph is intentional and small, because cooking by feel is a small-graph problem.
Suggestions are a thin layer of Claude on top of the graph, but the work is in the graph, not the model. The model only needs context the user already gave it.
Decisions I made differently
Notebook before recommender.
Most recipe apps are recommenders pretending to be notebooks. Remy is the inverse — the notebook is the product. Suggestions are an opt-in surface, not the homepage.
Flavor, not nutrition.
Macros are someone else's app. Remy speaks in flavor and texture and the things a cook actually says out loud.
Pin-as-primitive.
A pin is the smallest unit of memory the app stores — a dish, an ingredient, a combination. Everything else composes pins. That single primitive keeps the app small.
What I’d do next
Photo notes — the ability to pin a picture of the plate next to the words. Cooking is visual, and my notes shouldn't be only words.