top of page
Search

Fire Kitchen HQ: From Family Dashboard to a Cookbook That Knows What's in the Fridge

Writer: Andrew Walters
Andrew Walters
Nov 8
5 min read

Updated: Nov 9

Role: Designer & front-end developer · Year: 2026 · Client: Unifinity LLC (my own brand) and my family · Stack: React, JSX, Tailwind CSS, Vite, PWA · Workflow: AI-assisted development with Claude



The problem

In my house, "can we make tacos tonight?" was never a simple question. Answering it meant checking the fridge, remembering what each recipe needs, and doing budget math, all at once and usually in my head. Corporate teams solve this kind of problem with inventory systems. I wanted that same clarity for a family kitchen, in one shared tool.


Version 1: Kitchen HQ

I started from the question, not the features. Every screen had to help answer one of three things quickly: what do we have, what can we make, and what can we afford. That became four tabs, with the dashboard as the front door, plus a fifth Data tab added later for backups.



What version 1 did

  • Dashboard. An at-a-glance view of kitchen readiness with low-stock alerts, so the most important answer shows up first.

  • Inventory. Item tracking with quantity, unit, price, weight, and nutrition facts.

  • Recipes. Recipes built from inventory, with per-serving nutrition, missing-ingredient detection, and batch counts.

  • Budget Calculator. Combinatorial meal planning that generates several distinct plans of at least three recipes each, then ranks them.

  • Data. Backup and restore to a file, sample data for demos and a clear-all reset, so nothing is lost if a browser's storage is cleared.


Turning data into something readable

The budget planner produces a lot of numbers, so the interface does the reading for you. Plans are ranked with medal tiers, each one has a budget usage bar and stock status indicators, and expandable detail cards keep the summary clean until someone wants the specifics. Remaining budget stays visible the whole time.



Version 2: Fire Kitchen HQ, Unifinity Edition

Version 1 answered "can we make this?" for recipes we typed in ourselves. Version 2 merges it with our own cookbook, The Fire Recipes Cookbook, Unifinity Edition, into one app for a kitchen tablet. All 25 recipes from the book and its Vol. 2 expansion now live inside the pantry system, and every one of them can answer the question on its own: you can make this twice tonight, or you are missing two things and here is the list. It is designed as a gift for the Unifinity community first, with a paid edition planned later.

Fire Kitchen HQ home screen, Tonight's Lineup, showing recipes ready to cook with batch counts and cost per batch
Tonight's Lineup: every recipe that can be made right now, and how many times

The hard part: stock and recipes speak different units

The biggest problem in version 1 was one I had struggled with for a long time. We buy a 1.5 lb pack of ground beef, an 8 oz bag of cheese and two heads of garlic, but recipes ask for ½ lb, ¾ cup and 4 cloves. If the stock unit and the recipe unit don't match, the math breaks. I designed a conversion engine to close that gap:

  • Three families. Every amount becomes weight, volume or count. Within a family the conversion is exact: 3 tsp = 1 tbsp, 16 oz = 1 lb.

  • Ingredient profiles. Crossing families uses each ingredient's own numbers: about 111 g in a cup of shredded cheese, 4 g in a garlic clove, 400 ml in a can of coconut milk. A family's own measurements always win over the typical values.

  • Ask, don't guess. When a conversion needs a number the app doesn't have, it shows a "Needs a weight" prompt instead of inventing one. One measurement fixes every recipe that uses that item.

  • Staples stay simple. Salt, spices and splashes of oil are tracked as in stock or out, so nobody has to weigh a teaspoon of cumin.

Every ingredient line in the cookbook now converts automatically. The one exception, a slaw used inside the salmon tacos, is handled as a recipe within a recipe.

Fire Kitchen HQ pantry screen listing items in the units they were bought in, with the same amounts converted into cooking terms
The pantry: stocked the way it was bought, read back in cups, spoons and cloves

Designing from the book and the brand

The look comes straight from the cookbook and the Unifinity brand library. I matched the book's three typefaces (Righteous for display, Fraunces for titles and italic subtitles, Nunito Sans for body text), turned the cover's sunset and sound-wave motifs into the app icon and loading states, and gave each of the five chapters its own color. The dashboard is a dark "stage" for at-a-glance decisions, while recipe pages switch to the book's cream pages for comfortable reading at the counter. The copy follows Unifinity's PLURR values (Peace, Love, Unity, Respect, Responsibility), and the Bass Creatures appear only as small helper messages, like a Whimwisp suggesting where to look when one ingredient is missing.


What's new in version 2

  • Tonight's Lineup. The home screen shows how many times each recipe can be made right now, with filters for quick meals, Cool Zone dishes, full-heat dishes and anything missing just one or two items.

  • Cookbook pages. Each recipe shows your stock next to every ingredient in the recipe's own units, scales from one to four batches, and keeps the book's Pro Tips, Camp Mode, Remix and storage notes.

  • Cook this. One tap takes the ingredients out of the pantry, after showing exactly what will be used.

  • Shopping list. Missing items go to a shared list, which can be sent as a text, and checked items are put away into the pantry automatically.

  • Budget plans. Meal plans of three or more recipes that fit a weekly or monthly budget, using the prices the family actually paid.

  • Works offline. It installs on a tablet or phone like an app and keeps working without internet. Data from version 1 carries over automatically.

Fire Kitchen HQ recipe page for the Solar Flare-Saurus Rex Rice Bowl, showing pantry stock next to each ingredient and the method steps
A cookbook page with live pantry status beside every ingredient

Safety first

A cookbook app is trusted in a real kitchen, so safety was a design requirement. Meat recipes show their safe internal temperature, the hottest recipes carry the glove warning for habanero, and the juice shots keep the book's note that they are wellness foods, not medical treatment, including the grapefruit and medication warning. Unit conversions are labeled as estimates, and nutrition is shown only from labels the family enters. The app never guesses it.


How I built it

I built both versions with an AI-assisted workflow using Claude, the same approach I trained on through Anthropic's Claude Certified Architect program. For version 2 that meant turning the cookbook PDF into structured recipe data and checking it line by line, designing a style board before writing any app code, and testing the conversion engine against every ingredient in the book. I made the product, design and safety decisions, and used AI to move fast on extraction, code and testing. The app was then tested at tablet and phone sizes.


What's next

Next up: scanning a barcode or receipt to fill in nutrition and stock the pantry in seconds, one shared pantry that stays in sync across the family's devices, testing on kitchen smart displays, and a paid edition of the app and cookbook. You can try the current version at mellifluous-kashata-07c546.netlify.app.


Reflection

Dashboards work when they answer a real question before anyone has to ask it. Version 2 taught me that the hardest part is often invisible: the app only feels simple because the unit math, the safety notes and the data behind every recipe were designed with the same care as the screens. Whether it's a family deciding on dinner or a team tracking program performance, the job is the same: take scattered data and make the next decision obvious.

 
 
 

Comments


© 2026 by Andrew Walters

bottom of page