Sprint Reference

Build websites with AI

Universal rules

  1. 01When something goes wrong — copy the error, paste it into Claude, ask what it means.
  2. 02Two terminal tabs at all times — Tab 1 = Claude Code, Tab 2 = dev server.
  3. 03You are responsible, not Claude. Always review changes before they go live.
  4. 04Push and commit to GitHub after every task — every push is a restore point.

Daily use

Moving a project folder

If you reorganise files and move a project folder, the code itself doesn't break, but a few things need to be reconnected. Here's the checklist.

  1. 1

    Open a terminal in the new folder location

    Right-click the moved folder → Services → New Ghostty window here. Or cd manually.

  2. 2

    Verify GitHub is still connected

    The git remote travels with the folder, but check it's still there.

  3. 3

    Start Claude Code and ask it to verify everything

    Easiest first move — paste this in:

  4. 4

    Clear the .next build cache

    The cached build references the old folder path and will fail. Always do this after a move.

  5. 5

    Run a fresh build to surface any issues

  6. 6

    Run the dev server

    Test locally before pushing anything.

  7. 7

    Test BOTH the homepage AND /studio

    Open both. If /studio breaks, see Day 3 troubleshooting — Sanity Studio routes can fail after a Next.js upgrade.

  8. 8

    Push the fix(es) to GitHub

    If Claude made any code changes to fix the move, commit and push.

  9. 9

    Verify Vercel still deploys (it will if env vars are set)

    If Vercel build fails with 'Missing environment variable', see Day 3 troubleshooting — env vars don't sync from .env.local automatically.