Vibe Coding with Claude Code

What is vibe coding?

Vibe coding is building software by describing what you want in plain English. You use Claude Code inside VS Code to make changes to your app, and the Recursiv SDK handles everything on the backend — auth, AI, database, storage, deploys.

You focus on the product. Claude writes the code. Recursiv runs the infrastructure.

Prerequisites

Install these once:

1. VS Code — code editor (Windows, Mac, or Linux)
2. Claude Code extension — AI coding assistant inside VS Code
3. Node.js — LTS version
4. Git — version control
5. Expo Go — install on your phone from the App Store or Google Play

1. Clone your app

Open VS Code, then open the terminal (View > Terminal) and run:

$
git clone <your-repo-url>
$
cd <your-app-name>
$
npm install

Your team lead will send you a .env file — drop it in the project folder. This tells the app where the Recursiv backend is.

2. Run the app

$
npx expo start

Scan the QR code with your phone camera. The app opens in Expo Go and updates live as you make changes.

3. Make changes with Claude

Open the Claude Code panel in VS Code and ask for changes in plain English:

• “Change the home screen header color to blue”
• “Add a notes field to the settings form”
• “Show a loading spinner while data is fetching”
• “Make the list sortable by date”

Claude reads your codebase, edits the files, and you see the result on your phone in real time.

4. Save your work with Git

Git tracks your changes like version history in Google Docs.

Grab the latest updates

Do this before you start working:

$
git pull

Save and upload your changes

$
git add .
$
git commit -m "describe what you changed"
$
git push

• git add . — stages your changes (tells Git “I want to save these”)
• git commit -m "..." — saves a snapshot with a description
• git push — uploads so your team can see it

Think of it like: select all > save > upload.

Work on a branch

Branches let you experiment without touching the main app. Always work on a branch.

$
git checkout -b my-feature-name

Now you’re on your own copy. Make changes, then save and push:

$
git add .
$
git commit -m "added cool thing"
$
git push -u origin my-feature-name

When you’re happy with it, tell your team lead and they’ll merge it into the main app.

Go back to main

$
git checkout main
$
git pull

5. Undo everything

Made a mess? Reset all your local changes:

$
git checkout .

This restores every file to the last saved state. Your commits are safe — this only undoes uncommitted changes.

What Recursiv handles

Your app uses the Recursiv SDK to talk to the platform. You don’t need to manage any of this:

You focus on the frontend. Recursiv runs everything else.

Tips

• Ask Claude first. Before Googling an error, paste it into Claude Code. It can usually fix it.
• Small changes. Ask for one thing at a time. “Change the button color” is better than “redesign the whole page.”
• Commit often. Save your work every time something is working. You can always go back.
• Branch per feature. One branch for “add dark mode”, another for “fix login bug.” Keeps things clean.