Steps · 06. Build v1
  1. 00.Accounts
  2. 01.Life audit
  3. 02.Modules
  4. 03.Style brief
  5. 04.Storage
  6. 05.Build prompt
  7. 06.Build v1
  8. 07.Launch
  9. 08.Live in it
Step 06. of 08.Building

Build version 1 with Claude Code

This is where it comes to life. You'll paste your prompt, approve a plan, set up the database, then build one piece at a time while previewing as you go. Expect back-and-forth; that's normal and it's how it gets good.

Part A: Start the project

  1. 01.On your computer, make a folder for the project (e.g. Documents/the-nest).
  2. 02.Open the Claude desktop app and switch to Code.
  3. 03.Choose your new folder as the working folder.
  4. 04.Paste your build prompt from Step 5 and attach your inspiration screenshots.
  5. 05.Read the plan Claude Code shows you. Ask questions, change anything that's off, then say "Looks good, go ahead."

Claude Code will ask permission before running commands or creating files. Read each request; approving is normal for this project.

Part B: Set up your database

When Claude Code creates the SQL file:

  1. 01.Open your project at supabase.com (opens in a new tab) and go to SQL Editor.
  2. 02.Choose New query, paste the SQL Claude Code gave you, then choose Run.
  3. 03.Go to Table Editor. You should see one table per module. If so, it worked.
  4. 04.Check that each table shows Row Level Security as enabled. If any doesn't, tell Claude Code.

Part C: Add your keys

  1. 01.Ask Claude Code: "Create my .env.local file and tell me where to paste my Supabase keys."
  2. 02.Paste in your Project URL and publishable key from Step 4.

The .env.local file stays on your computer and is never uploaded to GitHub. That's by design.

Part D: Preview and build piece by piece

  1. 01.Ask Claude Code to start the preview. It will give you a local link like http://localhost:3000 to open in your browser.
  2. 02.Create your login (sign up with your email), then sign in.
  3. 03.Check the Today view. Then build modules one at a time: "Great, now build the Bills module."
  4. 04.After each module, test it: add something, edit it, delete it, refresh the page. If it's still there after a refresh, it's saving to Supabase.
  5. 05.Use the change request formula (in the Prompt library) for anything you want different.

Habits that save you hours

  • One change at a time. Five requests in one message means five chances for confusion.
  • Describe what you see, not what you think the fix is. "The bills total shows $0 even though I added two bills" beats "fix the math."
  • Screenshots help. Drag one in whenever something looks wrong.
  • Errors are information. Copy the full red error text and paste it to Claude Code.
  • Ask it to save your progress after each working module: "Commit this with a short description." (A commit is a save point you can return to.)

Before you move on

Step 06. checklist