Spec
Turn a plain-English prompt into concrete intent, constraints, and scope boundaries.
Describe what you want. The agent activates security-reviewed blocks, writes only the domain code, and proves every change with a real build. You walk away with standard React + TypeScript you fully own — never a no-code cage.
apps/scaffold/
The agent loop
No one-shot guesswork. Each turn parses intent, gathers context, plans a change set, builds it, and folds the result back in — so output stays consistent and reviewable.
Turn a plain-English prompt into concrete intent, constraints, and scope boundaries.
Snapshot the file tree, block manifest, and recent chat — bounded, never the whole repo.
Classify the work: activate a block, configure it, or generate a feature. Preview diffs first.
Apply patches behind a TypeScript + Vite gate. Broken builds never reach the preview.
The live preview updates. Your feedback starts the next cycle — iterate until it ships.
Runtime architecture
Generated apps talk straight to Supabase over a public key. A blue client zone is guarded by Row Level Security; a red server zone holds every secret. Authorization lives in the database, not in hope.
Frozen blocks
Auth, storage, admin, and RLS are reviewed once and frozen. The agent flips them on with deterministic recipes and spends its tokens on your actual product.
Supabase Auth, JWT sessions, and Row Level Security on every user-owned table by default.
Deterministic recipes flip a block from stub to enabled — no LLM ever rewrites security-critical wiring.
Secrets stay server-side. AI calls, admin metrics, and privileged writes run in the Deno red zone.
Tabs appear as blocks turn on — Users, Storage, AI usage — all gated behind RBAC.
A full reference app: upload a photo, get an AI health check, and browse history — end to end.
Runs on Vercel Hobby + Supabase free. Export the scaffold as a standalone repo whenever you like.
Why choose this platform
Tech stack
No bespoke framework to learn. It's the stack you already know — just scaffolded well.
{
"blocks": {
"auth": { "state": "enabled" },
"storage": { "state": "enabled" },
"ai": { "state": "enabled" },
"rbac": { "state": "enabled" }
}
}
FAQ
It's a proof-of-concept that mirrors Lovable's architecture. The blocks and RLS patterns are real and reviewable, but you should human-review generated RLS policies before shipping anything sensitive.
Everything. The output is standard React + TypeScript in your repo. Run pnpm export:scaffold
to lift it out as a standalone project — no runtime dependency on the platform.
Cross-cutting infrastructure is frozen. When you ask for "login," the planner runs a deterministic recipe that flips the auth block from stub to enabled and applies its migration — no LLM touches the internals.
Nothing to start. The default target is Vercel Hobby plus the Supabase free tier. Expect cold starts and occasional project pauses — fine for demos and internal tools.
Yes. The AI gateway runs in mock mode until you set a secret in Supabase, then routes real calls through an edge function so keys never reach the browser.
Open the builder, type what you want, and get real source code back — with a live preview and no lock-in.