How to export v0.dev projects and integrate them into existing Next.js codebases. Covers connecting v0 to GitHub, syncing with local development, and migrating from v0 to Claude Code. Use when transitioning from v0 to local development.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ncode-saas-toolkit-web:v0-to-codebaseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
v0.dev creates Next.js projects that deploy to Vercel. When you're ready to work locally with Claude Code, you need to connect v0 to your GitHub repo.
v0.dev creates Next.js projects that deploy to Vercel. When you're ready to work locally with Claude Code, you need to connect v0 to your GitHub repo.
v0 can connect directly to a GitHub repository:
Now you can:
If you started in v0 and want to go fully local:
# 1. Connect v0 to GitHub first (see above)
# 2. Clone the repo locally
git clone https://github.com/your-username/your-project.git
cd your-project
# 3. Install dependencies
npm install
# 4. Pull environment variables from Vercel
vercel link # Link to your Vercel project
vercel env pull .env.local # Pull env vars
# 5. Run locally
npm run dev
A v0 project is a standard Next.js app:
your-project/
app/
layout.tsx # Root layout
page.tsx # Home page
globals.css # Global styles (Tailwind)
components/
ui/ # shadcn/ui components
... # Your custom components
lib/
utils.ts # Utility functions
public/ # Static files
package.json
tailwind.config.ts
tsconfig.json
# 1. Initialize Supabase locally (if using)
supabase init
supabase link --project-ref your-project-ref
supabase db pull
# 2. Add CLAUDE.md for project context
# Claude Code will understand your project better with this file
Recommended CLAUDE.md for a v0 project:
# CLAUDE.md
## Stack
- Next.js 15 (App Router)
- Supabase (database + auth)
- Vercel (hosting)
- Tailwind CSS + shadcn/ui
- Polar.sh (payments)
## Commands
- `npm run dev` - Start dev server
- `supabase start` - Start local Supabase
- `vercel dev` - Dev with Vercel env vars
## Structure
- `app/` - Pages and API routes
- `components/ui/` - shadcn/ui components
- `components/` - Custom components
- `lib/` - Utilities and Supabase client
v0 connects to Supabase via the Vercel Marketplace. The environment variables are already set in Vercel. Pull them locally:
vercel env pull .env.local
This gives you SUPABASE_URL, SUPABASE_ANON_KEY, etc.
| Task | Use v0 | Use Claude Code |
|---|---|---|
| Quick UI prototyping | Yes | |
| Visual design iteration | Yes | |
| Complex business logic | Yes | |
| Multi-file refactoring | Yes | |
| Database migrations | Yes | |
| API routes with tools | Yes | |
| Deployment config | Yes |
The typical flow: Start in v0 for the UI, then move to Claude Code for everything else.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub dangogit/ncode-saas-toolkit-web --plugin ncode-saas-toolkit-web