Whole codebases, not snippets
Routes, components, server functions, schema and migrations — written together so the pieces actually fit.
Develpr
Describeit.Watchitgetbuilt.
A full workspace: plan, schema, files, live preview, terminal, secrets and deploy — every screen already wearing your brand.
Watch it think
It shows its working.
Including the part where it was wrong.
A real run, line by line — the question it stopped to ask, the error it hit, and the exact patch that fixed it. Scroll at your own pace.
Run in progress
8%- ReadingTwo unknowns before I touch a file: who books, and who gets paid.
Prompt to product
One paragraph in. A whole app out.
Prompt
- src/routes/index.tsxwritten
- src/routes/book.$slotId.tsxwritten
- src/lib/booking.functions.tswritten
- supabase/migrations/slots.sqlapplied
- src/routes/admin.tsxwritten
- previewrunning
Inside the workspace
Everything a build needs.
In one window.
Live sandbox preview
Every file lands in a running preview as it is written. No build step, no waiting.
A real terminal
Install, run and inspect from inside the workspace.
Errors it reads and repairs
Runtime failures stream back into the model, which patches the exact lines and verifies again.
Secrets it never sees
Keys go into an encrypted vault and reach the sandbox as environment values only.
Ship it
Push to a fresh GitHub repository and publish a live URL without leaving the tab.
Full stack, actually
It does not stop
at the frontend.
Most generators hand you a pretty shell with fake data behind it. Developr writes the database, the policies and the server logic too — then proves they run.
Data
Tables, policies, migrations
A real Postgres schema with row-level security and grants written in the same pass as the UI that reads it.
create table public.bookings (
id uuid primary key default gen_random_uuid(),
slot_id uuid not null references public.slots(id),
email text not null,
created_at timestamptz default now()
);
grant select, insert on public.bookings to authenticated;
alter table public.bookings enable row level security;Auth
Sessions, roles, guards
Sign-in, protected routes and role checks that live server-side, where they cannot be edited from a console.
export const confirmBooking = createServerFn({ method: "POST" })
.middleware([requireAuth])
.inputValidator(BookingInput.parse)
.handler(async ({ data, context }) => {
return hold(context.supabase, context.userId, data);
});Server
Functions, webhooks, jobs
Payments, email and scheduled work as typed server functions and verified public endpoints — not client-side wishful thinking.
POST /api/public/stripe-webhook
→ verify signature
→ mark booking paid
→ send confirmation email
cron 0 9 * * * → send day-ahead remindersBrand → build
Bring a brand.
Wear it everywhere.
Paste a URL, get a kit — palette, type, radius, voice. Hand that kit to the builder and every screen it writes comes out already dressed.
Extract a brand from a URL
The three moves
Talk. Look. Ship.
01 — ConverseAsk in plain language.
Follow-ups keep the whole project in context — no re-explaining what you already built.
02 — InspectSee the architecture.
File tree with sizes, imports and risk, a running preview, and a log of every edit.
03 — ReleaseHand it to the world.
Repository, environment values and a published URL — one pass, no context switch.
How it behaves
Six habits.
No exceptions.
- 01
Verifies before it claims
Nothing is reported as done until the build, the types and the run all agree.
- 02
Reads the actual error
Stack traces and command output go back in whole — not paraphrased into a guess.
- 03
Never invents an API
If a signature is unknown it opens the file and looks, or it asks you.
- 04
Files, not fragments
Whole routes, schema and server logic that compile together on the first pass.
- 05
Your brand, not a template
Palette, type scale, radius and voice come from your kit and stay consistent.
- 06
The thread stays open
Close the tab, come back tomorrow — the project, history and preview are still there.
How it goes
From a sentence to a running app.
- 01
Pick a brand
Reach for a kit you already extracted, or skip it and build bare.
- 02
Describe the product
One paragraph is enough. Plan, schema and files come back together.
- 03
Iterate, then ship
Patch, preview, test, publish — the thread stays open as long as you need.
Questions
Before
you start.
Multi-route web apps with a real database behind them: dashboards, marketplaces, booking and CRM tools, internal admin, content sites. Routes, components, schema, migrations, auth and server functions come out of the same run.
Say it once.
Come back to a running app.
Prefer the terminal? See plans and credits