Skip to main content
EnzRossi
FreeGuide/13 chapters

Your First Steps with AI Coding: Build a Real Next.js App with Cursor + Claude

A hands-on, follow-along walkthrough. One stack, one project, one workflow you'll keep using after the tutorial ends.

By EnzRossi EngineeringUpdated April 202633 min read
13 chapters/33 min read

Table of contents

What's inside

The first 2 chapters are free to read on this page. The full guide comes as a PDF you can save, print and share with your team.

  1. 01What You'll Build (and Why It's Worth 90 Minutes)A real deployed app, a real workflow, and the muscle memory to keep using both.
  2. 02What You Need Before StartingFive accounts, one terminal. None of them cost more than $20.
  3. 03Set Up Cursor with ClaudeFive minutes of configuration. You'll thank yourself later.
  4. 04Opus to Plan, Sonnet to BuildThe single most useful habit you'll learn from this guide.
  5. 05Step 1: Scaffold the Project (Sonnet)Get a working Next.js 16 project on your machine in 60 seconds.
  6. 06Step 2: Write CLAUDE.md and .cursor/rulesThe single most important step. Two files that change how every future prompt behaves.
  7. 07Step 3: Install Skills from skills.shReusable expert briefings the AI loads on demand.
  8. 08Step 4: Create the Project Plan (Opus, Agent Mode)Talk with Opus to split the whole project into phases, with a ready-to-paste plan prompt for each. The plan lives in the repo as the map for everything that comes next.
  9. 09Step 5: Phase 1, the Auth Foundation (new chat)First time through the loop. Open a fresh chat, plan with Opus in Plan mode, click Build to have Sonnet execute.
  10. 10Step 6: Repeat the Loop for Each Middle PhaseSame pattern, one fresh chat per phase. The number of trips depends on what your PLAN.md generated.
  11. 11Step 7: The Final Phase, Senior Review and ShipLast trip through the loop. Round out test coverage, get a senior review from Opus, and deploy to Vercel.
  12. 12When Things Go WrongA quick playbook for the six failures that catch most people.
  13. 13Cheat Sheet and Your Next 5 SessionsOne page of reference, plus five concrete projects to keep practicing.

Free preview

Chapter 1

What You'll Build (and Why It's Worth 90 Minutes)

A real deployed app, a real workflow, and the muscle memory to keep using both.

This is a follow-along guide. Open Cursor in one window, this document in another, and build with us. By the end you'll have a live, deployed app at your-app.vercel.app with:

  • Magic-link sign-in (no passwords)
  • Per-user todos: each user only sees their own
  • Create, edit, complete, and delete
  • Status filter: all / active / completed
  • Mobile-friendly UI

The app is small on purpose. The point is the workflow, not the feature set. Once you've shipped this one, the same workflow scales to whatever you build next.

Time budget

How you read it Time
Read every prompt, run every verification step, push back on the AI when it cuts corners ~90 minutes
Copy-paste, trust the agent, fix what breaks at the end ~30 minutes (and you learn less)

What you'll actually learn

The app is the artifact. The skills are the takeaway:

  • How to switch between Opus and Sonnet for different tasks (and why that saves money)
  • How to use Plan mode + the Build button so Opus plans and Sonnet executes in one click
  • How to draft a CLAUDE.md that the AI actually respects
  • How to use targeted .cursor/rules for file-scoped guidance
  • How to install and use community skills from skills.sh
  • How to plan a project at the right level: an overview PLAN.md split into phases, each with a ready-to-paste plan prompt that kicks off Plan mode for that phase
  • Why you open a fresh chat for each phase (and what happens when you don't)
  • How to debug fast with screenshots dropped into the chat
  • How to recover when the agent goes off the rails (it will, and that's fine)
Tip

If you only have 30 minutes, do sections 1 through 7 today and come back for the build steps tomorrow. The setup work compounds. The build steps are easier once your context layers are in place.

Chapter 2

What You Need Before Starting

Five accounts, one terminal. None of them cost more than $20.

Knock these out before you open Cursor. They take ~10 minutes and they unblock everything else.

What Cost Why you need it
Cursor Pro $20/mo The IDE, plus reliable access to Opus 4.7 and Sonnet 4.6. Cursor's subscription bundles model usage; you don't sign in with a separate Claude account. The free Hobby tier works for parts of this guide but limits how much you can use the top models. Download at cursor.com/get-started.
Node.js 20+ Free Required for Next.js 16. Install via nvm if you don't have it.
pnpm Free The package manager. npm install -g pnpm if you don't have it.
Supabase account Free Postgres + Auth. Create a new project before Step 5; the confirmation email lands while Cursor scaffolds.
Vercel account Free For deployment in Step 7. GitHub login is fine.
A terminal you're comfortable with Free iTerm2, Warp, the built-in macOS Terminal, or whatever you use.
Tip

Create the Supabase project right now, before you start coding. Pick a strong database password and save it in a password manager. The signup confirmation email and project initialization happen while Cursor is doing other work, so you save real time by getting it out of the way upfront.

Watch out

If you're on Cursor's free Hobby tier, you'll hit usage limits during the planning steps (Opus is the expensive model and the free tier rations it). You can still complete the guide, just expect to wait or upgrade partway through. Pro is the smoother experience.

Keep reading in the PDF

11 more chapters are in the free PDF, with every table, template and checklist ready to print.

  1. 03

    Set Up Cursor with Claude

    Five minutes of configuration. You'll thank yourself later.

    This guide assumes Cursor is installed. If it isn't, grab it from cursor.com/get-started and come back. Installers exist for macOS, Windows, and Linux. The download is free; you only need a paid plan if you want more usage than the…

  2. 04

    Opus to Plan, Sonnet to Build

    The single most useful habit you'll learn from this guide.

    Opus and Sonnet are both Claude models, both trained by Anthropic, both excellent. They're also priced very differently and they're good at different things. The mental model that makes this work:

  3. 05

    Step 1: Scaffold the Project (Sonnet)

    Get a working Next.js 16 project on your machine in 60 seconds.

    This is the easy step. The point is to get a clean foundation before we layer context on top of it.

  4. 06

    Step 2: Write CLAUDE.md and .cursor/rules

    The single most important step. Two files that change how every future prompt behaves.

    This is the context engineering step. Two files do most of the work:

  5. 07

    Step 3: Install Skills from skills.sh

    Reusable expert briefings the AI loads on demand.

    Skills are packaged units of procedural knowledge. Where CLAUDE.md is your project's constitution (always loaded, project-specific) and.cursor/rules are file-scoped surgical guidelines, skills are reusable instruction packs the AI loads on demand to do specific things well. Think of them as…

  6. 08

    Step 4: Create the Project Plan (Opus, Agent Mode)

    Talk with Opus to split the whole project into phases, with a ready-to-paste plan prompt for each. The plan lives in the repo as the map for everything that comes next.

    This is the methodology that separates "AI built me an app" demos from real production work. Asking an agent to "build me a todo app" produces a sprawling, half-finished diff that you can't review. Asking it to plan the project…

  7. 09

    Step 5: Phase 1, the Auth Foundation (new chat)

    First time through the loop. Open a fresh chat, plan with Opus in Plan mode, click Build to have Sonnet execute.

    Time to apply the loop from Step 4. Phase 1 sets up Supabase, magic-link auth, and route protection. Once this works, every later phase builds on it. We'll walk this one through in detail because it's your first trip through…

  8. 10

    Step 6: Repeat the Loop for Each Middle Phase

    Same pattern, one fresh chat per phase. The number of trips depends on what your PLAN.md generated.

    Phase 1 is shipped. Now the loop repeats once for each remaining phase your PLAN.md generated, except the final ship phase (which we cover in Step 7). For this todo app there are typically 2 to 4 middle phases (data…

  9. 11

    Step 7: The Final Phase, Senior Review and Ship

    Last trip through the loop. Round out test coverage, get a senior review from Opus, and deploy to Vercel.

    The middle phases are shipped. One phase to go: the final one in your docs/PLAN.md. For this todo app it's typically the "Tests, review, deploy" phase. We walk through it explicitly because two of its sub-tasks (the Opus senior review…

  10. 12

    When Things Go Wrong

    A quick playbook for the six failures that catch most people.

    Things will go wrong. The agent will get confused. A diff will be too big. A test will pass while the feature is broken. None of this means you're doing it wrong: it means you're doing it long enough to…

  11. 13

    Cheat Sheet and Your Next 5 Sessions

    One page of reference, plus five concrete projects to keep practicing.

    The whole guide compressed into a single page. Print it, save it to your wiki, paste it into the team Slack.

Send me the PDF

About the author

EnzRossi Engineering

Engineering, EnzRossi

Skip the hiring process

We already vetted 3,000+ engineers. Let us find yours.

Book a free 30-minute consultation and get your first shortlist in 3 days.