File
SMF·LOVABLE
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·LOVABLE

Can a prompt replace Lovable?

Developer tools — AI coding agents and developer workspaces

Not yet Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$25/moSource: lovable.dev · Checked on July 31, 2026
Per year
$300
Build time
One sitting
Votes
0 votes
YesAlmostNot yet (checked)

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: frontier models, context infrastructure, and execution safety
Exhibit Q Questions

Verdict

Generating a complete starter app — frontend, a database schema, and basic auth already wired together — from one descriptive prompt is a real weekend build once you accept a fixed, opinionated stack rather than Lovable's flexibility. What doesn't survive: Lovable's iterative multi-turn refinement polish and its one-click Supabase project provisioning.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a tool that generates a complete, runnable full-stack starter app from one descriptive prompt — frontend, database schema, and auth already wired together, not just isolated UI components like this catalogue's v0 entry. Use a fixed stack, Next.js, Postgres, a simple email/password auth library, so the model's job is filling in a known template rather than choosing infrastructure. Read a model key from ANTHROPIC_API_KEY or OPENAI_API_KEY. Given a prompt like 'a habit tracker where users log daily habits and see a streak', have the model infer a Postgres schema (users, habits, habit_logs tables with sensible relations), generate CRUD API routes for it, generate matching frontend pages (a dashboard, a habit list, a log-entry form), and wire auth so routes are protected. Write all generated files to a real project directory, run migrations against a connected Postgres database, and start the dev server so the user has something running immediately. Support one follow-up refinement prompt, such as 'also add a weekly summary view', that the model applies as a diff against the existing generated project, rather than only supporting a single one-shot generation. Do not build many-turn iterative refinement, one-click cloud database provisioning, or visual UI editing — those are out of scope; this generates a solid starting scaffold plus one refinement, not an ongoing conversational IDE. Requires an Anthropic or OpenAI API key, hosting, and a Postgres database.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 iterative multi-turn refinement polish
  • B.2 one-click backend project provisioning
  • B.3 a frontier model tuned for full-stack scaffolding specifically
  • B.4 visual editing of the generated UI

Prior art

Exhibit C — Why people still pay: frontier models, context infrastructure, and execution safety

Generating one starter scaffold is bounded work; iterating on it conversationally across many turns while keeping frontend, schema, and auth consistent with each change is the harder, ongoing product problem.

Questions

Does it wire up the database and auth automatically, or just generate frontend code?

Both — schema, API routes, and basic auth are generated and connected, not just UI components. That's the actual point of this build, distinct from a pure frontend-component generator.

Can I keep refining it conversationally, like Lovable?

One follow-up refinement is supported, applied as a diff to the existing project — but many-turn iterative refinement across a long session is real, harder product work this build doesn't fully replicate.

Does it provision a database for me automatically?

No — you connect an existing Postgres database yourself. One-click cloud database provisioning is real infrastructure integration Lovable has built.

What does it cost to run?

Hosting, a database, and model API usage per token — a full scaffold generation uses more tokens than a single chat message, so expect a noticeable but bounded cost per generation.

Receipt

Already built this yourself?