Build a recipe — see how it fits, what pairs, and what to expect.
How it fits together
● RECIPE LENS · closer = pairs more often · wildcards ring the edge
Add ingredients to see the map.
What to expect
Add ingredients to read the flavour profile.
Lens
What actually gets cooked together
Structurally central pairings
Shared flavour chemistry
Preference Shaper
Steer suggestions by taste — add up to 3 of your own, beyond what the recipe implies. Only Friends, Wildcards & the map shift; What to expect stays a true read of the recipe.
3 slots left
Recipe
Add an ingredient to begin.
Add ingredient
Recommendations
Add ingredients to see Friends & Wildcards.
Why I built this
I saw Jakub Radzikowski's and Josef Chen's Epicure paper on Hugging
face and thought it was so cool. I wanted to create a fast, intuitive,
snappy app based on their work for chefs and food lovers to use.
If you're wondering why the UI is arranged this way, it's because I
thought that it this app should be arranged like Chrono Trigger. IDK
why. It just has to be.
I also wanted proper flavour and aroma radar charts. I
wanted real "how sweet, how sour, how smoky is this" numbers for
every ingredient. I tried building them straight out of the paper's
vector embeddings. It didn't hold up: a sour soup came back with a
sourness score of zero, and durian and fermented tofu which were two
of the stinkiest foods I could think of, read as mild on every axis.
The embeddings are great at telling you which ingredients are alike;
they have no idea how strong anything actually tastes or smells. I
couldn't find a real source of intensity data to bolt on instead, so
I dropped it. Here's the mockup of what I wanted:
Flavour
Aroma
Mockup only; this data doesn't
exist yet. Maybe I'll crowd-source it one day.