> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.recursiv.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.recursiv.io/_mcp/server.

# 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](https://claude.ai/claude-code) inside VS Code to make changes to your app, and the [Recursiv SDK](/sdk/setup/installation-configuration) 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](https://code.visualstudio.com/) — code editor (Windows, Mac, or Linux)
2. [Claude Code extension](https://marketplace.visualstudio.com/items?itemName=anthropics.claude-code) — AI coding assistant inside VS Code
3. [Node.js](https://nodejs.org/) — LTS version
4. [Git](https://git-scm.com/) — 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:

```bash
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

```bash
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:

```bash
git pull
```

### Save and upload your changes

```bash
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.

```bash
git checkout -b my-feature-name
```

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

```bash
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

```bash
git checkout main
git pull
```

> **Tip**
>
> When in doubt, make a new branch. You can't break anything on a branch.

---

## 5. Undo everything

Made a mess? Reset all your local changes:

```bash
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](/sdk/setup/installation-configuration) to talk to the platform. You don't need to manage any of this:

| Feature       | What it does                   |
| ------------- | ------------------------------ |
| **Auth**      | Sign up, sign in, sessions     |
| **AI Agents** | Chat, streaming, memory        |
| **Database**  | Managed Postgres via the SDK   |
| **Storage**   | File uploads with signed URLs  |
| **Deploys**   | Production hosting in one call |

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.