A test kitchen for questions code can’t answer.
Jev’s Kitchen is an interactive React playground for exploring structured AI decisions through food. Ask an everyday question and get back an answer your application can use—not another block of unstructured text.
| Demo | Decision type | What it answers |
|---|---|---|
| Dominant Taste | Choice |
Which basic taste leads in a food or dish? |
| Ingredient Compatibility | Noul |
Is an ingredient typical in a conventional version of a dish? |
| Spice Meter | Score |
How spicy should a dish be expected to taste, from 0–10? |
Each demo includes sample inputs, loading and error states, and a confidence or probability visualization when the result provides one.
pnpm install
cp .env.example .env
pnpm devOpen the local URL printed by Vite. The app automatically uses deterministic mock responses when no API key is configured, so you can explore it immediately.
To use live Jev responses, add your TypeSafe API key to .env:
TYPESAFE_API_KEY=your_typesafe_api_key
JEV_MODE=auto
JEV_MODEL=autouses live Jev whenTYPESAFE_API_KEYis present and falls back to the mock adapter otherwise.mockalways uses deterministic local responses.livealways uses Jev and requiresTYPESAFE_API_KEY.JEV_MODELis optional; leave it blank to use the SDK’s current default model.
React interface → local API → Jev adapter → structured decision
↘ mock adapter
The API key stays on the server. The local API, Jev adapter, schemas, and isolated mock implementation live in server/, keeping provider details out of the browser and the UI.
| Command | Purpose |
|---|---|
pnpm dev |
Start the app and local API in development |
pnpm build |
Type-check and create a production build |
pnpm preview |
Preview the production build locally |
React · TypeScript · Vite · TypeSafe
