Part 3 of my guide to building custom tools with Ai.

Making pizza with Claude

Monday, 18 August, 2025

I cook a lot, bake a lot. Thus I spend a lot of time with a calculator, scaling recipes up and down. Until one Saturday morning when I realized – why am I doing this math shit when I could be building an app for it?

Making pizza with Claude

The 15 minutes of baking fame

My recipe for pizzas is a tweaked version of Sandra Mastios “The One”: 12 pieces of dough, 240g each. Easy peasy … but now I’m invited to a restaurant to make pizzas for an event where they will serve 5 different small dishes on their patio. Guests? anything between 50 and 150 people. To top it off the restaurant has a green Michelin star so regular large sloppy pizzas won’t cut it. After a bit of testing and discussiong with the chefs we decide to go for 50g size pizzas.

Now the 12 piece 240g dough recipe has to be scaled down to make 50 gram balls … but also up to serve 150 people. Vad i helvetet?

I’m standing in my kitchen knowing I need to make at least 3 test batches before the event. My plan is to first test size and baking time, then toppings, flavour and estetics. Lastly the third test batch will be a validation that I can repeat the pizzas.

Each batch takes 5 days of fermentation and each has to be identical. So I need at least a month to be sure I can produce a solid recipt for the event.

I think you get the idea. There is no way I can rely on a calculator and manual calculations for this.

Base recepie:

Total dough weight: 2898 g

Converting that to 50 g doughballs will give about 57 doughs. To get the right amount of flour for 150 dough balls I need to … (1360/50)x150, and so on, through six ingredients … satan i gatan … we can all see that this won’t work and it will be a huge source of errors.

But, I’m a ux designer. I solve problems for a living. Why am I manually doing this like it’s 1999?

The use-case is bigger then I thought

As I stood there, calculator in hand, I realized this wasn’t just about one recipe. I have dozens of recipes: Japanese milk bread, foccacias, pixel bread, surfer buns, drunken Irishmen loafs. Sometimes I want to make 5 loaves, sometimes just 10 small rolls. Every single time, it’s the same tedious math.

Describing the solution

So I opened Claude and said:

Can you please provide a simple php-based pizza dough calculator.

It should be based on this recipe:

3 gram fresh yeast
1080g cold water
1360g Tipo-00 flower
340g high protein flower
65g salt
50g olive oil

The recipe makes 11 dough balls with a weight of 260g each.

The functionality of the calculator shall be:

- Dropdown with how many dough balls I want to make.
- Desired weight of the dough balls
- Scaled recipe is presented
- Total dough weight is presented

That’s it. No technical specifications, no user stories, no wireframes. Just a clear description of the problem I wanted to solve.

Claude Desktops interface is super simple, chat/conversation to the left. Artifacts to the right. Artifacts is Claudes «browser» browser where apps, visualizations, graphics, games or whatever you build is run.

Within 15 minutes, we had a woking app (pun intended …).

But wait, how do I get the code from Claude to my server?

Once Claude has cooked up your app code, you need to get into your web server.

All three methods require you to have setup a server (mamp or other), and created Sites/your-project

Claude Desktop

Mild – perfect for beginners

Step-by-step

  1. Chat

    • Describe what you want to build
    • Claude creates code in artifacts (the interactive sidepanel you see above)
    • Review and refine until you’re happy
  2. Download the code

    • Click the download button on Claude’s artifact
    • Save the file(s) to Sites/your-project
  3. Test and iterate

    • Start your mamp server
    • Open http://localhost:8888/your-project/ in your browser
    • If it works, great! Something broken? Go back to Claude, describe the issue
    • Claude fixes it in a new artifact
    • Go back to Step 2: download and replace the old files

Pros: Simple, visual, you see every step

Cons: Lots of manual copying when making changes

Claude Desktop + file access

Medium – control and convenience

Step-by-step

  1. Enable filesystem access

    • In Claude Desktop, click the «Search & Tools» menu in the bottom left
    • Look for «Filesystem» and enable it
    • This gives Claude direct access to your computer’s files and folders
    • You might need to grant permission when prompted
  2. Start building

    • Describe your app to Claude
    • Say: «Please create the files directly in my /Users/[yourname]/Sites/your-project/ folder»
    • Claude will create index.php, styles.css, data.json etc. right where they belong
    • No more downloading and copying files!
  3. Test and iterate

    • Open http://localhost:8888/your-project/
    • When you want changes, tell Claude: «Update the login function in auth.php»
    • Claude modifies the actual file directly in the your-project folder
    • Refresh your browser to see changes instantly

Pros: No more copying files, real-time collaboration, Claude understands your entire project structure

Cons: Need to enable filesystem access, requires some comfort with file paths

Claude Code

Spicy – productivity for the brave

Step-by-step

  1. Install Claude Code

    • Go to Claude Code documentation
    • Follow installation instructions for your system
    • You’ll use Terminal (that black window that looks scary but isn’t)
  2. Navigate to your project

    cd ~/Sites/your-project
    

    (This tells your computer to «go to the my-project folder")

  3. Start Claude Code

    claude
    
    • This opens a chat interface right in your terminal
    • Claude can now directly create, edit, and run files
  4. Code and iterate

    • Describe what you want: «Build a invoice processing app with file upload»
    • Claude creates multiple files simultaneously
    • Test immediately: Claude can run the app and show you errors
    • Iterate fast: «The upload isn’t working» → Claude fixes it instantly

Pros: Lightning fast development, Claude handles technical setup, professional-grade workflow

Cons: Terminal can be intimidating initially, requires more technical comfort

Which method should you choose?

Start with Method 1 for your first app, then jump straight to Method 2.

Save Method 3 for when you’re building apps regularly and want maximum speed.

The best workflow is the one you’ll actually use. Don’t let complexity stop you from building. Start simple and evolve your process as your confidence grows.

… back to the pizzas!

The app Claude built for me is beautifully simple:

The app in action

Since the first version I have added the possibility to comment and add new recepies.

I started with the copy-paste Method 1, but when I needed to add features like recepie-notes and adding new recepies I switched to Method 2: Claude Desktop with fileystem access.

My pizza calculator folder

My base recipe looks like this in the .json-file:

«name»: «Sandra Mastio - The One»,
«pieces»: 11,
«weight»: 260,
«ingredients»: {
    «Fresh Yeast»: 3,
    «water»: {
        «Cold Water»: 1080
    },
    «flour»: {
        «Tipo-00 Flour»: 1360,
        «High Protein Flour»: 340
    },
    «Salt»: 65,
    «Olive Oil»: 50
}

From tedious task to time saver

Building and styling this app took less than an hour. Using it saves me time and eliminates the frustration and errors of manual calculation.

But more importantly, it proved a concept: I could identify a real problem in my life and solve it with custom software. Not find a workaround or live with the inconvenience, but actually solve it completely.

That realization was intoxicating.

… and off we go!

This simple baking calculator became my springboard to building custom tools. It showed me that the barrier between «person with problem» and «person with custom solution» was waaaaay much lower than I’d imagined.

If I could solve my weekend baking math in under an hour, what other annoying tasks could I eliminate from my life?

Next up: How I turned the most dreaded part of freelancing – writing proposals – into a 45-minute task instead of an 8-hour ordeal.

But how did the pizza event go?

Well, absolutely fantastic. It was a lot more stressfull than I thought and baking pizzas al’a minute was perhaps not the best of ideas when there were 140 to make.

Here are some pictures from the prepp and the event.

The final product served at the event The Restaurang Jord crew :-)