Vibe Coding Checklist

Free tool · Lovable, Figma Make or any AI builder · Checked against the official docs, October 2026

Prototype to product

How do I move my Lovable or Figma Make prototype into a real codebase I own?

Get the code into a GitHub repository you own (Lovable syncs on every plan; Figma Make pushes one way), open it with an AI coding tool (Claude Code, Codex, Cursor or Gemini CLI), and give it an AGENTS.md rules file before the first change. Then sort out the backend: Lovable Cloud can stay or move to your own Supabase, and Figma Make's key-value store needs real tables. Change the sign-in addresses, and move the domain last.

Answer a few quick questions. "Not sure" is a fine answer to any of them. You'll get a move plan in the right order for your setup, each step with a way to know it worked, plus a starter rules file, your first prompts (for any AI coding tool) and an inventory of where everything lives.

No prototype yet? Start from zero: set up an AI coding tool and build your first real app this week.

Words you'll see, in plain English
GitHub / repository
Where your code is stored, with every version kept. Like Figma's version history, for code. A repository ("repo") is one project there.
AI coding tool
An AI that works directly in your project's files: it reads the code, makes changes and runs commands, and asks before anything risky. Claude Code, OpenAI's Codex, Cursor and Gemini CLI are examples.
Backend
The part people don't see: where data is saved, how sign-in works, and code that runs on a server instead of in the browser.
Supabase
A popular backend service: a database, sign-in and file storage in one. Lovable Cloud and Figma Make both use it underneath.
Host
The service that puts your app on the internet at an address, like Vercel or Netlify.
Environment variables
Settings kept outside the code, like your database address. Secret ones (keys, passwords) must never end up in the browser.
Row-level security (RLS)
Database rules that decide which rows each person can read or change. It's what stops one user from seeing another user's data.
Migration
A file that describes one change to the database, so changes are saved and repeatable instead of clicked by hand.
AGENTS.md
A plain text file of rules in your project. Claude Code, Codex and Cursor read it at the start of every session. (Gemini CLI reads GEMINI.md unless you tell it otherwise.)
Where did you build it?
Where is its data saved?
Where is its data saved?
Where is its data saved?
Move the backend too?
After the move, will you still edit in Lovable?
Where will it live on the internet?
Do people sign in?
Does it take payments?
Does it have its own domain (like yourapp.com)?
Who will own it?
App name (optional, for your rules file)

Built in your browser. Nothing you type here is sent or saved.

Common questions

Can I keep editing in Lovable after moving the code out?

Yes. Lovable's GitHub sync is two-way on one branch, so pushes from your AI tool to that branch pull back into Lovable. Don't edit in both at once: if they drift apart, Lovable pushes to a lovable-sync branch and edits made only in Lovable can be lost.

Can Figma Make code sync back after I download it?

No. Figma's docs say changes you make to the code can't automatically be pushed back to Figma Make. Treat the repository as the product and Make as a sketchpad.

Do my users have to reset their passwords if I leave Lovable Cloud?

Not if you follow Lovable's route. The full database export includes user accounts with their password hashes, so people keep their passwords. Sessions don't carry over, so everyone signs in once more.

Is Figma Make's Supabase database ready for real users?

Figma's docs say Make sets up basic key-value stores in Supabase's Postgres, not a full SQL database. For a real product, design proper tables with row-level security.

Is this official?

No. It's an independent guide by Andrew Adams, checked against Lovable, Figma, Supabase, Vercel, Anthropic, OpenAI, Cursor and Gemini documentation in October 2026. It isn't a professional audit, and nobody here will move your app for you.

Sources

An independent guide, not affiliated with Lovable, Figma, Supabase, Vercel, Anthropic, OpenAI, Cursor or Google. These tools change often; if a menu has moved, the prompts still work. Written by Andrew Adams. See also: Lovable launch checklist · Cursor and Claude Code · Supabase · Start from zero.