Claude Code Build Night · Part 3 · Free

Build the MVP

Bring an idea. Leave with a live app.

How the night runs.

Twenty minutes of AI news, one live build, then five-minute demos from the room.

  1. 01

    Idea

    One idea, one screen, one job.

  2. 02

    Spec

    Claude Code interviews us and writes one page.

  3. 03

    Build

    Slice by slice, checked against the spec.

  4. 04

    Ship

    Live on Vercel, open on your phone.

The deck.

Every slide from the night, free to share. Open it full size to step through.

Build the MVP · slidesOpen full size →

Tonight's example.

The app we build on the night, from a one-page spec. Start from it, or write your own with the interview prompt.

SPEC.mdWhat's for Dinner

What's for Dinner

Type what's in your fridge. Get three dinners you can make tonight.

The one jobTurn what's in my fridge into dinner tonight.

  • Next.js
  • Better Auth
  • Neon
  • AI SDK
  • Vercel
Done when
  • Sign up, sign in and sign out on a phone
  • Three recipes in under 15 seconds
  • Only my ingredients, plus salt, oil and pepper
  • My history stays mine after a refresh
  • Live on a Vercel URL
The full spec
# What's for Dinner

## Problem
At 6pm people stare into the fridge, see ingredients instead of meals, and order takeout.

## User
Someone at home in the early evening, on their phone, with a few ingredients and twenty minutes.

## The one job
Turn what's in my fridge into dinner tonight.

## Out of scope
- No meal planning, calendars or grocery lists
- No recipe database or search
- No sharing or social features
- No nutrition tracking
- No dark mode or settings

## Screen
Phone first:
1. Sign in or sign up with email and password (Better Auth)
2. One input: "What's in your fridge?" with ingredients as chips, and a "Find dinners" button
3. Three dinner cards: name, minutes, the ingredients it uses, and five short steps
4. "Your dinners" below: past results, newest first, only yours

## Data
Better Auth's own tables for users and sessions, plus two tables: `dinners`: `id`, `user_id`, `ingredients` (text array), `recipes` (JSON, three items), `created_at`; and `ai_calls` (see Money).

## Money
The pricing model and the free limit come from RESEARCH.md. No payments yet.
- `ai_calls`: `id`, `user_id`, `model`, `input_tokens`, `output_tokens`, `cost` (from providerMetadata.gateway.cost, if present), `created_at`. Insert one row for every AI call, including failures.
- Before each call, count this month's `ai_calls` for the user on the server. At the free limit (10 a month unless RESEARCH.md says otherwise), skip the call and show "You've used your 10 free dinners this month. More soon." in place of an error.

## AI
One server route calls Claude Sonnet through the AI SDK and Vercel AI Gateway with the ingredient list and returns exactly three recipes as structured output (name, minutes, ingredients used, five steps). Recipes only use what was given plus pantry basics (salt, oil, pepper). 15-second timeout; on failure, show "Couldn't find dinners right now" and save nothing.

## Done when
- [ ] On a phone-width screen, I can sign up, sign in and sign out
- [ ] Typing four ingredients and tapping "Find dinners" shows three recipes in under 15 seconds
- [ ] Every recipe only uses my ingredients plus salt, oil and pepper
- [ ] "Your dinners" shows my past results after a refresh, and another account can't see them
- [ ] Every "Find dinners" tap adds one ai_calls row with my user id and token counts, and the 11th request this month shows the free-limit message without calling the model
- [ ] It's live on a Vercel URL

## Bonus
"Snap your fridge": upload a photo instead of typing. A vision-capable Claude model, through the AI SDK and AI Gateway, turns the photo into the ingredient chips, which the person can edit before tapping "Find dinners". Photos under 5 MB, never stored.

The prompts.

Every prompt from the deck, in order. Open one, copy it, paste it into Claude Code, Codex or any coding agent.

  1. 01
    Let Claude Code interview you
    Interview me about an app idea until we can write a one-page spec.
    
    Ask one question at a time and wait for my answer. Cover:
    - Who it's for, and the moment they'd open it
    - The one job it does
    - What it will not do in the first version
    - What the screen shows
    - What data it keeps, if any
    - What done looks like: how we'll know it works
    
    Push back when an answer is vague. When you have enough, write SPEC.md with these sections: Problem, User, The one job, Out of scope, Screen, Data, Done when. Keep it to one page.
    
    Then stop and wait for my OK before writing any code.
  2. 02
    Planning skills from Matt Pocock
    Type these one at a time. They are commands, not a prompt to paste.
    
    1. In your terminal:
       claude plugin install mattpocock-skills@claude-plugins-official
    2. In Claude Code:
       /reload-plugins
    3. /setup-matt-pocock-skills
       Choose local markdown files as the issue tracker.
    4. /grill-me
       Then describe your app idea and answer its questions.
    5. /to-spec
       Run it once the plan holds up.
    6. Then paste this prompt:
       Copy the spec you just wrote to SPEC.md at the repo root. Trim it to one page with these sections: Problem, User, The one job, Out of scope, Screen, Data, Done when.
  3. 03
    Set up the stack
    Read SPEC.md. Set up the project for it one step at a time, and stop after each step.
    
    1. Create a Next.js app with TypeScript, Tailwind CSS and the App Router:
    npx create-next-app@latest build-night --ts --tailwind --app --eslint --use-npm --yes
    2. Move SPEC.md into build-night.
    3. Stop and tell me to do three things myself, then wait until I'm back:
       - cd build-night
       - run npx neon@latest init, which signs me in and sets up Neon's MCP server and agent skills for this folder
       - start Claude Code again inside build-night
    
    Do not build any features yet.
  4. 04
    Build it slice by slice
    Read SPEC.md.
    
    First, the foundations. Do these one at a time and stop after each:
    1. Database: if .env.local has no DATABASE_URL, use the Neon tools to create a database for this project and save its connection string to .env.local. Never print secrets.
    2. Auth: add Better Auth with email and password, following its current docs for Next.js and Postgres. Generate BETTER_AUTH_SECRET into .env.local and create its tables.
    3. AI: install the AI SDK with npm install ai. Ask me to create an AI Gateway API key in the Vercel dashboard and add it to .env.local as AI_GATEWAY_API_KEY myself. Wait until I tell you it's done.
    
    Then create only the table SPEC.md needs. Restate the spec in five lines and list the smallest slices that get us to every check under Done when, in order. Wait for my OK.
    
    Build one slice at a time. After each slice, run it, tell me what to open in the browser, and wait for me before starting the next one. If something in SPEC.md is unclear, ask me instead of guessing. Do not add anything listed under Out of scope.
  5. 05
    Steering is the skill
    That isn't what SPEC.md says. Here is what I saw: [describe what happened on screen]. The spec says: [quote the line]. Explain in one sentence why they differ, fix it, and tell me what to check. Don't change anything else.
  6. 06
    Polish skills from Emil Kowalski
    Install Emil Kowalski's skills for this project. In my terminal I will run:
    npx skills@latest add emilkowalski/skills
    
    Wait until I tell you it's installed. If you can't see the skills yet, tell me to restart Claude Code.
    
    Then run /break-ui on the main screen. Try worst-case data: long names, an empty list, a huge count. Fix what breaks, one issue at a time, and show me each fix at phone width.
  7. 07
    Ship it
    Run every check under Done when in SPEC.md and tell me which pass. Fix any that fail.
    
    Then get this live. Create a GitHub repo and push to it, connect it to Vercel, and add DATABASE_URL to the Vercel project's environment variables. Ask me before any step that needs my login. When the deploy finishes, give me the live URL.
  8. 08
    Teach it to see
    Bonus round: add "Snap your fridge". Stop after each step.
    
    1. Add a section called Bonus to SPEC.md: a "Snap your fridge" button next to the ingredients box. The person uploads a photo (under 5 MB, never stored). A vision-capable Claude model turns it into ingredient chips the person can edit before tapping "Find dinners". If the photo has no food in it, say so instead of guessing.
    2. Use the AI SDK through Vercel AI Gateway with a "provider/model" string. Check the AI Gateway model list for the current vision-capable Claude Sonnet model ID instead of guessing.
    3. Add one server route that sends the image and returns a plain list of ingredients, with a 15-second timeout. On failure, keep the ingredients box as it was and show "Couldn't read that photo."
    4. Show me the button at phone width with a real photo, then redeploy. Don't commit any keys.

The toolkit.

Everything we build the app with on the night, one job each.

Bring an idea. Leave with a live app.

Wed Dec 9, 2026 · 5:30 - 7:30 PM MST · Workuity Biltmore. Free, and open to anyone building with AI.

Harbor at dusk · Phoenix, Arizona