Build, augment, and ship apps from a chat.
PromptFloe turns a natural-language prompt into a running web app — then lets you keep working on it through the same chat. Generate, edit, deploy, and harden your app without leaving the conversation.
#What PromptFloe is
PromptFloe is a multi-agent app studio. You describe what you want, the orchestrator scaffolds a real React + Vite app in a WebContainer sandbox, and the live preview boots in your browser. From there you can:
- Edit files in the embedded Monaco editor — changes hot-reload in the preview within milliseconds.
- Continue the conversation to make changes ("add a pricing page", "switch to dark theme", "swap in real customer data").
- Run
skills— sub-agents like/roast,/seo-audit, or/seothat critique or augment your app. - Deploy to Netlify in one click, sync to GitHub, and pick up where you left off across sessions.
#Key concepts
Five concepts you'll see throughout the docs. Understanding the difference up front makes the rest much easier.
Chat workbench
The /chat page. Two panels: conversation on the left, code + live preview on the right. Every message routes through the multi-agent build pipeline or — if it starts with / or @ — through a skill.
Skills
Sub-agents you invoke from chat. Two kinds: critique (returns markdown) and augmenter (modifies your app's files). Run with /alias for built-ins or @alias for your custom ones.
Workspace context
The single document every skill reads first. Your product, audience, brand voice, words to never say. Set it once and every skill stays on-brand without re-pasting.
Augmenters
Special skills that modify your generated app's file tree — /seo, /marketing, /a11y, /pwa, and more. Toggle them as chips above the prompt input to bake them into the next generation.
Channel agents
Different from skills. Agents wired into Slack, Discord, webhooks, or HTTP — they handle messages outside the chat. Live at /agents.
Tiers
Plan controls daily skill quotas + augmenter access. Free runs critique only; Basic and up unlock augmenters. Manage at /settings/billing.
#How the pieces fit together
A typical session flows from prompt to shipped app in five stages:
- Plan — landing prompt input, optional augmenter chips, optional template.
- Build — multi-agent pipeline scaffolds the app in a WebContainer sandbox.
- Review — code + preview in the workbench; iterate by chatting or editing files directly.
- Augment — run skills (
/seo,/roast) or queued augmenters to harden + improve. - Ship — one-click deploy to Netlify, optional GitHub auto-sync.
The RunHeader at the top of every chat shows which stage you're in (Plan → Build → Review → Ship), with the active stage colored and previous ones marked done.
#Where to go next
Generate your first app and run a skill against it in under 5 minutes.
How to invoke skills from chat. Autocomplete, aliases, args.
/seo, /marketing, /a11y — skills that modify your generated app.
Daily limits per tier, what unlocks at each plan, how to cancel.