03 / Flow starters
Start ahead.
Stay in Flow.
Two deliberately opinionated Next.js templates. They choose the stack, tooling, and deployment for you, so a new product deploys on day one. Want other choices? Use Flow's skills in your own repo.
Single application
flow-next
One focused Next.js app with a public Assistant, a protected Operator, and agent-facing MCP surfaces.
Multi-package application
flow-mono
A minimal Turborepo with a Next.js app in apps/web and shared UI components in packages/ui.
Common foundation
Built for humans
and agents.
Capability
Agent-ready
A public Assistant with chat, GenUI, and MCP beside a protected Operator console, so humans and agents share one product.
Interoperability
Standards-minded
MCP Streamable HTTP, shared tool names documented in docs/INTEROP.md, and lint, types, and tests behind one pnpm qa.
Delivery
Vercel-first
Every push to main deploys with no environment variables set, and inference runs through Vercel AI Gateway.
Capabilities reflect each repository's current README; verify them against the template revision you start from.
Compare
Same contract. Different shape.
| Aspect | flow-next | flow-mono |
|---|---|---|
| Layout | Single Next.js app | Turborepo: apps/web + packages/ui |
| Shared UI package | No; components live in the app | Yes; packages/ui |
| Agent surfaces | Assistant, Operator, MCP, MCP Apps | Assistant, Operator, MCP, MCP Apps |
| Vercel project root | Repository root | apps/web |
| Choose it when | One product, one deployable app | You expect shared packages or more apps |
Prefer to talk? Say “start a Next.js project” and the start skill initializes a new project from either starter with verified setup and its own Git history.