Initial Setup (Windows)

Install the required tools on Windows and verify your development environment.

💻 Using a Mac? See Initial Setup (Mac).

Install the Claude Desktop App

In vibe coding, you build by giving instructions to Claude. First, install the Claude Desktop app and log in.

  1. Download: Get the Windows app from claude.com/download
  2. Install: Run the downloaded installer
  3. Log in: Launch the app and log in with your Claude account (contact an admin if you don't have one)

The "Ask Claude" prompts throughout this guide can be pasted into the Claude Desktop app (Claude Code) or the Claude extension in VS Code.

Prerequisites Checklist

Before you start vibe coding, make sure you have these tools installed:

ToolPurposeRequired
Claude DesktopThe Claude app (includes Claude Code)✅ Yes
wingetPackage manager for Windows✅ Yes
Node.js / npmJavaScript runtime✅ Yes
pnpmFast package manager✅ Yes
GitVersion control✅ Yes
Git LFSLarge file storage for Git✅ Yes
GitHub CLI (gh)Create PRs from terminal✅ Yes
VS CodeCode editor with Claude extension✅ Yes

About terminals: We recommend Windows Terminal or the VS Code integrated terminal (PowerShell or Git Bash) for command-line work. After installing a tool, open a new terminal before running the verification commands.

Verify Your Installation

Already have some tools installed? Check which ones you need:

Ask Claude to verify your setup
Claude prompt
Check if all the required development tools are installed on my Windows machine: - winget - Node.js (v20+) / npm - pnpm - Git - Git LFS (git-lfs) - GitHub CLI (gh) Show me the version of each tool. If any tool is not installed, use Claude Code to install it for me.
Or run it yourselfpowershell
# winget
winget --version
# Git
git --version
# GitHub CLI
gh --version
# Node.js
node --version
# npm
npm --version
# pnpm
pnpm --version
# Git LFS
git lfs version

Expected Output

You should see version numbers for each tool:

Expected output (in command order)text
v1.x.x
git version 2.x.x.windows.x
gh version 2.x.x
v22.x.x
10.x.x
9.x.x
git-lfs/3.x.x (GitHub; windows amd64; go 1.x.x)

If any tool shows "command not found" (or "is not recognized"), follow the installation guide below.

Installation Guide

The steps below use winget (Windows Package Manager), which makes installing each tool relatively easy.

1. Check winget (Windows Package Manager)

Recent versions of Windows 10/11 include winget by default. Run the following in PowerShell or Command Prompt to confirm it works:

Check wingetpowershell
winget --version

If it's not installed or not available, install "App Installer" from the Microsoft Store, or consider installing the tools manually.

2. Install Git

Git is the version control system:

Install Gitpowershell
winget install Git.Git

After installation, open a new terminal and verify:

Verifypowershell
git --version

If a version number is shown, you're all set.

Manual install: You can also download and run the installer from git-scm.com/download/win. The default installer settings are fine unless you have specific preferences.

3. Install GitHub CLI

The GitHub CLI (gh) is the official CLI tool for working with GitHub from the terminal. It allows Claude to create Pull Requests directly:

Install GitHub CLIpowershell
winget install GitHub.cli

# Verify in a new terminal
gh --version

First-time setup: After installing, link your GitHub account:

Authenticate with your GitHub accountpowershell
gh auth login

Follow the on-screen instructions to authenticate (a browser will open). Choose:

  • GitHub.com
  • HTTPS
  • Authenticate with a web browser

4. Install Node.js and npm

Node.js is the JavaScript runtime and npm is its package manager. Installing Node.js also installs npm. For development, use the LTS (Long Term Support) version:

Install Node.js (LTS)powershell
winget install OpenJS.NodeJS.LTS

# Verify in a new terminal
node --version
npm --version

If both show version numbers, you're all set.

Manual install: You can also download and run the installer from nodejs.org/en/download.

5. Install pnpm

pnpm is our package manager of choice for the monorepo:

Install pnpmpowershell
npm install -g pnpm

If PowerShell shows a "running scripts is disabled on this system" error, see Troubleshooting below.

6. Install Git LFS

Git LFS (Large File Storage) is required for handling large binary files in the repository:

Install Git LFSpowershell
winget install GitHub.GitLFS

# In a new terminal, initialize Git LFS for your user account
git lfs install

After running git lfs install, you should see:

Expected outputtext
Git LFS initialized.

7. Install VS Code with Claude Extension

VS Code is our recommended editor with the Claude extension for AI-assisted coding:

Install VS Codepowershell
winget install Microsoft.VisualStudioCode

After installing VS Code:

  1. Open VS Code
  2. Go to Extensions (Ctrl+Shift+X)
  3. Search for "Claude" by Anthropic
  4. Click Install

Clone the Repository

Once all tools are installed, clone the repository:

Ask Claude to clone the repo
Claude prompt
Clone the vibe-coding-platform repository from https://github.com/CoworkingKitchen/vibe-coding-platform and install dependencies.
Or run it yourselfpowershell
# Clone the repository
git clone https://github.com/CoworkingKitchen/vibe-coding-platform.git

# Navigate to the directory
cd vibe-coding-platform

# Install all dependencies
pnpm install

Setup Quiz

Quiz

Which command should you use to install dependencies in this monorepo?

Troubleshooting

"Running scripts is disabled on this system" error

If you see this error when running pnpm or other tools, open PowerShell as Administrator and run:

Allow script executionpowershell
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Then open a new terminal and try again.

"winget" is not recognized

Install "App Installer" from the Microsoft Store. If that doesn't resolve it, run Windows Update to get the latest version.

A tool is installed but the command is not recognized

The PATH (command search path) is loaded when a terminal starts. Close all open terminals and open a new one, then try again.

Next Steps

Once your setup is complete, proceed to the Workflow to start your first contribution.