Schemaflow
Sketch a database in plain English, get migrations you can run
About
Describe your app in a few sentences and Schemaflow drafts the tables, relations and indexes as a diagram you can drag around. When it looks right, export Drizzle or SQL migrations.
How it was made
Shared by the maker. Numbers are their own estimate.
- Build time
- 3 weeks
- AI spend
- $44
- Prompts
- ~150
- Written by AI
- 85%
Agents
Claude Code
75% of the workDiagram editor and exporters
v0
25% of the workInitial canvas UI
Build recipe
The code is on GitHub. If you’d rather build it yourself than fork it, paste this into your own agent.
Written by Claude Code
From the project’s code and history · 354 words
Build a developer tool called Schemaflow: sketch a database in plain English, get migrations you can run.
What it does
Describe your app in a few sentences and Schemaflow drafts the tables, relations and indexes as a diagram you can drag around. When it looks right, export Drizzle or SQL migrations.
Stack
Use Next.js, Drizzle, Postgres. The original was built with Claude Code and v0 in 3 weeks, for about $44 in AI usage.
How it fits together
- A focused tool with one main view and a small backend
- Local storage or SQLite for saved runs
- A clear config file so it fits into existing projects
Build it in this order
- Scaffold the project and a single page or command that runs end to end
- Build the core operation and test it with three tricky real examples
- Add saving, history and comparison
- Write a README with a two-minute quick start
- Add tests that run in CI
Tools to connect
- Postgres MCP: runs each generated migration against a scratch database
- Supabase MCP: one-click deploy of the result
A prompt that worked: Schema from a paragraph
From the app description below, propose a Postgres schema. Use singular table names, uuid primary keys, created_at/updated_at on every table, and explicit ON DELETE behaviour on every foreign key. Before writing the migration, list the three decisions you were least sure about and why.
Watch out for
- Developers will judge it in the first minute, so the quick start has to work exactly as written
- Avoid hidden network calls; say what leaves the machine
Done when
- The quick start works on a clean machine
- The core operation has tests for edge cases
- Errors say what went wrong and how to fix it
Before writing code, ask me up to five questions about who this engineering developer tool is for and what the first version must do. Then work in small steps: after each one, tell me how to try it and wait for my feedback.
Discussion
3 comments
- Lena Vogt6 hours ago
Love how focused this is. One thing: the empty state took me a second to understand. Maybe show an example right away?
- Kenji Mori1 day ago
What did the agent struggle with most? Always curious where people had to step in.