Quick start
Generate your first app, run a skill against it, and deploy it to Netlify — in under 5 minutes. No setup, no install. Everything happens in the browser.
#Before you start
- A PromptFloe account. Sign in at
/auth/signinwith email or GitHub. - A workspace. The first one is auto-created on signup. You can switch workspaces from the top bar.
- A modern browser with cross-origin isolation support. Chrome, Edge, and Firefox all work; we set the COOP/COEP headers needed by the WebContainer sandbox.
#Step-by-step: from prompt to live app
Open the chat workbench
Go to /chat. The page splits into two panels: a chat conversation on the left, and a code-and-preview area on the right. On first load the right panel is empty until your first build finishes.
Describe what you want to build
Type a natural-language prompt into the input at the bottom. Be specific about pages, features, and tone. The orchestrator works best when it has enough to plan a real app, not just a single screen.
A pricing page for a CRM SaaS targeting small agencies.
Three tiers (Starter / Growth / Scale), monthly + annual toggle,
testimonials, and a sticky CTA. Modern dark theme, violet accents.(Optional) Toggle augmenter chips
Above the prompt input you'll see chips like /seo, /marketing, /a11y, and /pwa. Click any of them before sending — they queue up and run automatically right after the build pipeline finishes, layering their changes onto your generated app.
Augmenters are paid features (Basic and up). Free accounts will see a small lock icon and an upgrade prompt if they try to queue them.
Hit Enter and watch the build pipeline
The right panel switches to a build progress view. You'll see five stages animate through: Plan → Files → Code → Review → Ship. On a cold start the whole pipeline takes 30–90 seconds depending on prompt complexity.
When the build finishes, the preview tab boots a real Vite dev server in your browser via WebContainer. Edits to any file hot-reload within ~200ms.
Iterate by chatting
Don't open the file tree yet — just keep talking. Try things like "switch to a serif heading font", "add a FAQ section above the footer", or "use real-looking testimonials with photos from unsplash.com". Each follow-up rebuilds the relevant files only.
Run a critique skill
Type /roast and hit Enter. A no-mercy product critic reviews the app and surfaces issues. Try other built-ins:
/seo-audit— meta tags, OG, structured data review/eli5— explain the app like the user is five/copywriting— proofread headlines and CTA copy
Skill output streams into a card in the chat — it does not modify your app's files. (Augmenters do.)
Deploy to Netlify
Click the Deploy button in the right panel header. A modal opens and asks for a site name (or autogenerates one). One click and the static build is uploaded to Netlify. You'll get a live HTTPS URL and the Deploys panel updates with the run.
From here you can add a custom domain, enable GitHub auto-sync, or share the link with a teammate.
#What just happened, technically
Behind the scenes, your prompt went through a 5-stage multi-agent pipeline. Each stage is a separate LLM call with its own role:
- Planner — drafts a file manifest and information architecture from your prompt.
- Files agent — emits the file tree (paths only), partitions work into chunks for parallel codegen.
- Code agents — fan out to write each file's contents. They run concurrently and stream into the workspace as they finish.
- Reviewer — checks for missing imports, unused symbols, and obvious bugs across files.
- Ship stage — boots the WebContainer, installs dependencies, runs
vite dev, and exposes the preview URL.