Everything you need to go from “I have an idea” to “my users are using it.” Pick a section, or read top-to-bottom in about 20 minutes.
Create your first build in under a minute. Pick a template or start from a blank prompt.
How prompts, builds, and sandboxes fit together. Worth reading once.
When you want to step out of chat: file tree, in-editor diff, GitHub sync.
Connect Supabase, Stripe, Resend, and other building blocks via the connector library.
Set up sign-in for your generated apps with Supabase Auth or a custom provider.
Every prompt directive, every shadcn component we bundle, every keyboard shortcut.
Open the home page, type one or two sentences into the prompt cockpit, hit Cmd+Enter. Be specific about the kind of app, not the implementation: 'A recipe app where I can save and tag dishes' is better than 'A Next.js app with a Postgres database'.
Buildliy spins up a Next.js sandbox and streams the generated UI back into the preview pane within seconds. You can interact with the preview while the rest of the project is still being written.
Anything you'd normally do in a designer's review (move this here, change that color, add a missing state) you do by talking to the agent. Each round produces a new version you can roll back to.
Connect a GitHub repo from /settings and push your project. From there you can deploy to Vercel, run it locally, or hand it off to a developer.
A build is one round-trip with the agent. A project is a sequence of builds that share a sandbox, a file tree, and a chat history. A template is a curated starting prompt that produces a known-good first build. Everything else — fragments, RBAC, integrations — sits on top of those three.
Looking for something specific? Browse the FAQ or ask us directly.