Nuhu Shaik

Free playbook

The Claude Code Setup Playbook

Never set up a code editor? Start here. Every step shown on screen, from installing VS Code to opening the first app you built with Claude.

New to all this? I’ll guide you through it on a 1:1 call.

Request a call

Before you start

What you’ll set up

  1. VS CodeThe app your project lives in
  2. Claude CodeClaude, inside VS Code, building it
  3. GitHubA saved copy of every version

What you need

  • Mac or WindowsmacOS 13 or newer, or Windows 10 or 11
  • Claude Pro$20 a month. Step 7 covers it
  • An emailFor your free GitHub account
  • About an hourTick each step off as you go

No coding experience needed. Your place is saved on this browser, so you can stop and come back.

Two ways to start

Do it yourself, or take the shortcut.

On your own

Follow this guide, step by step. Free.

Start at step 1

With me

One hour, live, on your computer. I’ll guide you through every step, so you skip months of figuring it out.

Request a callCAD 200

Not worth it? Tell me within 24 hours for a full refund.

  • 3 years building software
  • 3,200 monthly active users on Ayah
  • 700 paid users on Drum Breaker
  • Caterpillar web HMI for power systems

01

VS Code

The free app your project lives in. You’ll do everything from here.

About 10 minSteps 1 to 60 of 6 done

Code copied out of chats ends up scattered across your Downloads.

One folder per project, open in VS Code.

Where you’re headed

  1. FilesEverything in your folder
  2. EditorThe file you’re reading
  3. TerminalWhere commands run
  4. ClaudeWhere you ask for changes
  1. Step 1 of 34

    Download VS Code

    VS Code is the free app you’ll build in, made by Microsoft.

    Open the download page and click the button for your computer.

    You’ll seeThe download lands in your Downloads folder.

    Doesn’t look like this?
    • Already use Cursor? The same steps work there: it’s built on VS Code.
    • On a Chromebook or an iPad? You’ll need a Mac or a Windows PC for this.
  2. Step 2 of 34

    Install it

    Mac

    Open the download in your Downloads folder. In the window that opens, drag Visual Studio Code onto the Applications folder.

    Windows

    Open the download. Choose I accept the agreement, then keep clicking Next, leaving the boxes as they are. On the GitHub Copilot CLI page, choose Don’t add the copilot command: it’s a different AI, with its own paid plan. Then click Install, then Finish.

    You’ll seeVS Code is in your Applications folder (Mac) or your Start menu (Windows).

    Doesn’t look like this?
    • No GitHub Copilot CLI page on Windows? Carry on: it doesn’t show on every computer.
  3. Step 3 of 34

    Open VS Code

    VS Code may offer you its own AI, GitHub Copilot. Skip it: your AI is Claude.

    Open VS Code from your Applications folder (Mac) or the Start menu (Windows). If it asks you to sign in to use GitHub Copilot, click Continue without Signing In.

    You’ll seeVS Code is open. It’s empty for now: your project goes in next.

    Doesn’t look like this?
    • Your Mac asks if you’re sure you want to open it? Click Open.
    • No sign-in screen? That’s fine: not everyone gets one.
    • To keep VS Code in your Dock on a Mac: Control-click its icon there, then Options › Keep in Dock.
  4. Step 4 of 34

    Make your project’s folder

    VS Code works on one folder at a time. Every app you build gets its own.

    Click File › Open Folder…, go to Documents and click New Folder. Name it my-first-app (small letters, a dash between words), then click Open. On Windows the button says Select Folder.

    You’ll seeMY-FIRST-APP shows at the top left. A bar about Restricted Mode shows too: that’s normal, step 6 turns it off.

    Doesn’t look like this?
    • Opened the wrong folder? Click File › Open Folder… again and pick my-first-app.
  5. Step 5 of 34

    Open the terminal

    The terminal is where you paste commands. You’ll only need a few, and they’re all in this guide.

    Click Terminal › New Terminal. VS Code asks you a question first: that’s the next step.

  6. Step 6 of 34

    Trust your folder

    New folders open in Restricted Mode, which keeps the terminal and Claude switched off. It’s your own folder, so it’s safe.

    Click Trust Folder & Continue.

    You’ll seeThe terminal opens at the bottom, and the Restricted Mode bar is gone.

    Doesn’t look like this?
    • No question, and the terminal just opened? Your folder is already trusted. Carry on.
    • Clicked Cancel? Click Terminal › New Terminal again.

Stuck on any step? Copy this into claude.ai (the free plan works) and add a screenshot of your screen.

Stuck? Ask Claude
I'm setting up VS Code and Claude Code for the first time on my [Mac or Windows PC]. I'm stuck at this step: [the step]. Here's what I see: [what's on your screen, or paste a screenshot]. What do I do? Explain it simply, one step at a time.

Free playbook

Where should I send it?

The rest opens right here, and I’ll email you the link and the PDF for your computer.

  • Claude Code
  • GitHub
  • Your first app
  • Your own problem
  • Cheat sheet

No spam. You’ll get the playbook now, then new guides and the occasional offer from Nuhu Ventures Inc. Unsubscribe any time. Privacy and contact details

02

Claude Code

Claude inside VS Code: it reads your files, makes the changes and runs your app.

About 15 minSteps 7 to 150 of 9 done

A chat can’t see your files, so you copy code by hand.

Claude works in your folder. You approve each change.

  1. Step 7 of 34

    Get Claude Pro

    Claude Code needs a paid Claude plan: Pro, or higher. The free plan doesn’t include it.

    Open the plans and choose Pro: $20 a month in the US, less if you pay yearly (prices vary by country). Sign up with your email, or log in if you already use Claude.

  2. Step 8 of 34

    Install Git

    Git saves versions of your project, so you can always go back. Claude uses it for you.

    Mac

    Click in the terminal, paste this (⌘V) and press Enter. A box asks to install the developer tools: click Install, then Agree, then Done when it finishes. It takes a few minutes.

    git --version

    Windows

    Download Git for Windows and open it. Click Next on every page, then Install. When it’s done, quit VS Code and open it again.

    You’ll seeRun git --version in the terminal again: it shows git version and a number.

    Doesn’t look like this?
    • It showed git version straight away, with no box? You already have Git. On to the next step.
    • No terminal after opening VS Code again? Click Terminal › New Terminal.
  3. Step 9 of 34

    Install Node.js

    The apps Claude builds for you run on Node.js, on your own computer.

    Open the Node.js download page. Skip the box of code at the top: you want the installer button under it.

    Mac

    Click macOS Installer (.pkg). Open it and click Continue until it’s done. It asks for your Mac’s password: the one you log in with.

    Windows

    Click Windows Installer (.msi). Open it, accept the license and click Next until it’s done.

    Then quit VS Code and open it again, so its terminal finds Node.js.

    You’ll seeRun node -v in the terminal: it shows a version number, starting with v.

    Doesn’t look like this?
    • It says node isn’t found? Quit VS Code completely (⌘Q on a Mac) and open it again.
    • No terminal after opening VS Code again? Click Terminal › New Terminal.
  4. Step 10 of 34

    Add Claude Code to VS Code

    This puts Claude inside VS Code, with everything it needs: nothing else to install.

    Click Extensions on the left (the icon of four squares). Search for claude code. On Claude Code for VS Code, by Anthropic, click Install.

    Doesn’t look like this?
    • Pick Claude Code for VS Code, by Anthropic. Others with similar names, like Chat for Claude Code, aren’t made by Anthropic.
    • Asked to trust the workspace? Click Trust Workspace & Install.
  5. Step 11 of 34

    Trust Anthropic

    VS Code asks the first time you install from a company. Anthropic makes Claude.

    Click Trust Publisher & Install.

    You’ll seeClaude Code’s Install button turns into a gear: it’s installed.

  6. Step 12 of 34

    Open Claude

    Click ✻ Claude Code at the bottom right of the window.

    You’ll seeClaude’s panel opens on the right, headed Claude Code.

    Doesn’t look like this?
    • Not there? Quit VS Code and open it again.
    • Still not there? Press ⇧⌘P (Ctrl+Shift+P on Windows), type Claude Code and choose Open in New Tab.
    • VS Code’s own Chat panel is a different AI, GitHub Copilot. Use the one headed Claude Code.
  7. Step 13 of 34

    Sign in

    Click Claude.ai Subscription. Your browser opens: log in to Claude and allow access. Then come back to VS Code.

    You’ll seeClaude’s panel shows a box at the bottom for you to type in.

    Doesn’t look like this?
    • It says you need a plan? Your account has to be on Pro (step 7).
    • The browser didn’t open? Click Claude.ai Subscription again.
  8. Step 14 of 34

    Choose Manual

    Claude starts in Auto, where it changes files without asking. In Manual it asks first, so you see each change.

    Click the mode under the box you type in, and choose Manual. Claude remembers it.

    Doesn’t look like this?
    • Later, once you trust it, switch to Auto and Claude works without stopping to ask.
  9. Step 15 of 34

    Tell Claude you’re new

    Your first message. Claude saves it as a file it reads at the start of every chat, so it always explains as it goes.

    Copy this, click in Claude’s box, paste it and press Enter. Claude shows you the file first: click Yes.

    Tell Claude I’m new
    I'm new to coding. Create a CLAUDE.md for this project that says: explain every change in one plain sentence, ask before installing anything, and tell me how to see each change in my browser. Call me [your first name].

    You’ll seeCLAUDE.md appears in your files on the left. That’s Claude’s first change.

    Doesn’t look like this?
    • Green lines are what Claude adds. Red lines would be what it takes out.
    • Nothing happened? Press Enter, or click the arrow by the box.

Hit your limit? Your plan resets every five hours, with a weekly limit on top. Type /usage in Claude’s box to see when.

Stuck on the setup? I’ll guide you through it on a 1:1 call.

03

GitHub

A saved copy of every version of your project. If something breaks, you go back.

About 10 minSteps 16 to 210 of 6 done

One bad change can wipe out the version that worked.

Save a version every time something works.

What you’ll have

my-first-appPrivate

  1. Undo “Make the sidebar collapsible”Just nowWorks again
  2. Make the sidebar collapsible5 min agoBroke the page
  3. Add a sidebar of pages1 hr ago
  4. First versionYesterday

The page is blank since your last change. Go back to the last save point that worked.

Undone, as a new save point, so nothing is lost. The page loads again.

  1. Step 16 of 34

    Make a GitHub account

    GitHub keeps every version of your project online, private and free.

    Sign up with your email, a password and a username. Then verify your email: GitHub sends you an email to confirm it’s you.

    You’ll seeYou can log in at github.com.

    Doesn’t look like this?
    • Don’t skip verifying your email: GitHub won’t let you publish until you do.
    • No email from GitHub? Check your spam folder.
  2. Step 17 of 34

    Tell Git who you are

    Every save is signed with your name, so GitHub knows it’s yours.

    Copy this into Claude’s box, fill in your name and email, and press Enter. Claude asks to run two commands: click Yes for each.

    Tell Git who I am
    Set up Git on this computer with my name, [your name], and my email, [the email you use on GitHub].

    You’ll seeClaude says it’s done.

  3. Step 18 of 34

    Publish your project

    Click Source Control on the left (the icon that looks like a branch). Then click Publish to GitHub.

    Doesn’t look like this?
    • No Publish to GitHub button? Check your folder is trusted (step 6) and Git is installed (step 8). Then quit VS Code and open it again.
  4. Step 19 of 34

    Sign in to GitHub

    VS Code asks to sign in: click Allow. Your browser opens: sign in to GitHub and allow VS Code. Then come back to VS Code.

    Doesn’t look like this?
    • On Windows a second sign-in window may pop up. Sign in there too.
  5. Step 20 of 34

    Choose private

    Only you can see a private project.

    VS Code names it after your folder. Click Publish to GitHub private repository. If it asks which files to include, leave them all ticked and click OK.

    You’ll seeVS Code says Successfully published. Click Open on GitHub to see your project there.

  6. Step 21 of 34

    Save as you go

    Each save is a point you can always go back to.

    From now on, every time something works, copy the first prompt into Claude’s box. If something breaks, the second takes you back. You never have to type a Git command.

    Save my progress
    Save my progress: commit everything with a short note on what changed, and push it to GitHub. What works now: [what you just got working].

    Go back
    Something broke. Go back to my last save point that worked, from before [the change that broke it]. Don't delete any history: undo it as a new save point, then tell me what changed.

    Doesn’t look like this?
    • Claude says it couldn’t send your saves to GitHub? Click Sync Changes in Source Control: VS Code sends them for you.

Keep it private, and never put a password or an API key in your project.

04

Your first app

Rebuild an app you already use, one piece at a time, start to finish.

About 20 minSteps 22 to 280 of 7 done

A big, vague idea gets you a big app you can’t check.

Copy an app you use, one piece at a time.

How every build goes

  1. 1Ask for one piece“Add a sidebar of pages.”
  2. 2Try itOpen the localhost link Claude gives you
  3. 3Save it“Save my progress.”
  4. 4Next pieceUntil it does what you need
  1. Step 22 of 34

    Pick an app to rebuild

    Copying an app you already use is the fastest way to learn: you know how it should work, so you can tell when Claude gets it right.

    Pick one below and click Copy prompt. Never built anything? Pick an Easiest one.

    • A to-do listlike TodoistEasiest

      You’ll learnAdd a task, tick it off, delete it

    • A link pagelike LinktreeEasiest

      You’ll learnYour own page, your links, your colours

    • A notes applike NotionEasy

      You’ll learnPages, a sidebar, saving as you type

    • A flashcard quizlike DuolingoEasy

      You’ll learnQuestions, answers and a score

    • A task boardlike TrelloMedium

      You’ll learnColumns, cards and drag and drop

    • A booking pagelike CalendlyMedium

      You’ll learnA calendar, time slots and a form

  2. Step 23 of 34

    Paste it into Claude

    Click in Claude’s box, paste (⌘V on a Mac, Ctrl+V on Windows) and press Enter. Claude lists the app’s features, smallest first.

  3. Step 24 of 34

    Pick the first piece

    One piece at a time: each one small enough to check before the next.

    Type the number of the feature to build first, like 1, and press Enter.

  4. Step 25 of 34

    Say yes as it builds

    In Manual mode Claude asks before each file it changes and each command it runs.

    Read what it wants to do, then click Yes. Seen enough of its changes? Click Yes, allow all edits this session, and it stops asking about files.

    Doesn’t look like this?
    • npm install downloads the parts your app is built from. That’s normal: it’s why you installed Node.js.
    • Not sure what it does? Ask in the box under the buttons: What does this do?
  5. Step 26 of 34

    Open your app

    When Claude says your app is running, click the localhost link it gives you. If VS Code asks, click Open.

    You’ll seeYour app opens in your browser. localhost means it runs on your own computer: only you can see it.

    Doesn’t look like this?
    • Claude gave you a command instead, like npm run dev? Paste it into the terminal and press Enter, then click the link it prints.
    • No link at all? Ask Claude: How do I open my app in the browser?
    • Closed the page? Click the same link again. If it won’t load, ask Claude to start the app again.
  6. Step 27 of 34

    Tell Claude what’s off

    Your first try won’t be perfect. Saying exactly what you see is how you get it right.

    Copy this into Claude’s box and fill in the blanks. A screenshot helps: paste it into the box too.

    Fix what I see
    When I [what you did], I expected [what should happen], but [what happened instead]. Fix it, then tell me exactly how to check it.

  7. Step 28 of 34

    Save it, then the next piece

    When it works, ask Claude to save your progress. Then ask for the next feature. Repeat until it does what you need.

    The next piece
    That works. Save my progress, then build the next piece: [the next feature]. Only that, then tell me exactly what to click to check it.

    You’ll seeYou built an app with Claude, one piece at a time, and every piece is saved on GitHub.

05

Your own problem

Next, build the thing you wish existed: for your work, your money, your week.

About 30 minSteps 29 to 340 of 6 done

Random ideas stall: you don’t need them, or they can’t be built.

Find a real problem. Check it. Then build it small.

  1. Step 29 of 34

    Spot a problem

    The best first app fixes something that annoys you every week.

    Look for these in your week. Can’t think of one? Let Claude interview you.

    • A job you do by hand every week
    • An app you pay for but barely use
    • A spreadsheet you dread opening
    • Something you keep forgetting
    • The same copy and paste, again and again
    Find my problems
    Interview me to find problems in my life I could solve with a small app. Ask about my work, my money, my home and the apps I pay for, one question at a time, up to 10. Then list 5 problems, ranked by the time or money a fix would save me, with how hard each is to build. About me: [what you do most days].

  2. Step 30 of 34

    Check it’s worth it

    Three ticks or more: build it. Fewer: pick another one.

    • You hit it every week
    • It costs you time, money or stress
    • You’d use the fix yourself
    • A small version fits in a weekend
  3. Step 31 of 34

    Check it can be built

    Some ideas need data or services you can’t get. Better to know before you start.

    Ask Claude before you build: copy this with your idea in it. Claude rates the idea like a traffic light.

    • Build itOnly your own data: lists, forms, numbers, reminders
    • DoableNeeds a service, like email, payments, maps or AI
    • Rethink itNeeds data you can’t get, like another app’s private data
    Can it be built?
    I want to build [your idea, in a sentence]. Before we start, tell me straight: can this be built as a simple web app on my computer? Rate it green (only my own data), amber (needs a service like email or payments: say which) or red (needs data I can't get). Then give me 3 ways to solve the problem, including ones with no app, and recommend the simplest.

  4. Step 32 of 34

    Pick the simplest fix

    Maybe you don’t need an app at all.

    Claude’s answer gives you three ways. Build only if building wins.

    1. Way 1An app you already haveSet up once
    2. Way 2A spreadsheetA formula or two
    3. Way 3Your own appWhen building wins
  5. Step 33 of 34

    Or start from an idea

    No problem in mind yet? Pick one that sounds like your week and copy its prompt.

    • A client trackerWork

      Instead ofa messy spreadsheet

    • An invoice makerWork

      Instead ofediting last month’s invoice

    • A subscription trackerMoney

      Instead ofsurprise renewals

    • A bill splitterMoney

      Instead ofmaths in the group chat

    • A savings trackerMoney

      Instead ofguessing if you’ll get there

    • A meal plannerHome

      Instead ofdeciding at 6 pm

    • A chore chartHome

      Instead ofarguing whose turn it is

    • A content calendarGrowth

      Instead ofposting whenever

    • A workout logGrowth

      Instead ofyour Notes app

  6. Step 34 of 34

    Build it, ugly

    A plain app that works beats a beautiful one you never finish.

    Paste your prompt into Claude and build it the same way as your first app: one piece at a time, saving as you go.

    Not pretty. It works, and it’s yours.

    Build it small
    I [the problem, like track my clients in a messy spreadsheet]. Build me the simplest web app that fixes it, just for me. Ask me up to 5 questions first. Don't worry about how it looks.

Not sure your idea is worth building? I’ll help you pick it and plan it on a 1:1 call.

You’re set up.

You have everything a builder has. Now it’s practice.

  • VS Code, with your project’s folder
  • Claude Code, signed in and asking before each change
  • GitHub, saving every version
  • Your first app, built and saved

What next

Cheat sheet

The words and keys you’ll use.

Keep it next to your keyboard.

Words

Terminal
Where commands run
Extension
An add-on for VS Code
Git
Saves versions of your project
GitHub
Keeps them online, safe
Commit
One save point
Push
Sends save points to GitHub
localhost
Your app, on your computer
Node.js
What your apps run on

In Claude Code

@
Point at a file
Paste
Show it a screenshot
Esc
Stop Claude
Rewind
Undo its changes: hover a message
/clear
A fresh chat
/usage
What’s left of your plan
/
Every other command

1:1 setup call with Nuhu Shaik

One call with me will save you months.

If you’re a beginner, it’s the shortcut: I’ll guide you through your setup and your first app on your own computer, and show you what took me 3 years to learn.

  • One hour, live
  • On your own project
  • CAD 200
  • How to set up VS Code, Claude Code and GitHub the right way
  • How to prompt Claude so it builds what you mean
  • How to plan your first app, one piece at a time

Rather take the shortcut? Request a 1:1 call at nuhushaik.com/resources/setup#call

Saves me hours every day. You help me a lot.
Gibi Saini · Media agency
3,200
monthly active users on Ayah
700
paid users on Drum Breaker
Caterpillar
web HMI for power systems
Takes a minute. I read every request myself.Not worth it? Tell me within 24 hours for a full refund.

Request a 1:1 call

I’ll reply myself within two business days.
Step 1 of 4
One call, or regular calls?