Quickstart
Give your agent a brief and get to a local review with the shortest path.
Licensed source
If you bought VibeKit, start on Source code in your VibeKit account. Download the licensed source and use Copy agent setup. Keep the supplied license key and agent token private; your coding agent stores them only in gitignored .vibekit/auth.json for future licensed updates.
For a new product, extract the VibeKit download, open that folder in your coding agent, then use the install prompt below. For an existing VibeKit product, do not restart the install flow; use Update VibeKit to latest. instead.
Recommended install prompt
Open the extracted VibeKit folder in your coding agent and give it this request:
Read START_HERE.md and AGENTS.md. Build my product using the VibeKit workflow.
Use a disposable local database and mock services first. Do not deploy yet.
Product brief:
[who it is for, main workflow, business model and visual direction]The agent handles checkout state, local setup, implementation and verification.
Existing VibeKit project
Open the existing product checkout in your coding agent and say:
Update VibeKit to latest.The shipped $update-to-latest-template workflow checks the official VibeKit Source API for the certified update path, prepares only the next supported hop, preserves customer changes, verifies the result, and repeats only when another certified hop is required. It never retrieves licensed VibeKit source directly from GitHub.
Manual fallback
If you need to start the template yourself:
bun install
bun run setup:local --disposable
bun run devOpen http://localhost:3000.
The setup command prepares local secrets when needed, a disposable PostgreSQL database, migrations and generated Prisma code. Keep .env private.
Use real provider credentials only after the local product is ready to review.