The spec-to-prototype stack
Claude turns a PRD into contracts, Eraser draws the topology, v0 scaffolds the UI. Not a Cursor repo map.
Who owns what
Claude
The spec — entities, APIs, acceptance notes. Not the diagram and not the Next app.
Try Claude (opens in a new tab)Eraser
The topology — ER and cloud boxes from that markdown. Not frontend code.
Try Eraser (opens in a new tab)v0
The UI scaffold — screens from the spec. Not the database schema.
Try v0 (opens in a new tab)
How to use this stack
- Paste the PRD into Claude. Get entities, routes, and what is explicitly out of scope.
- Eraser compiles that into a map you can put on the ticket. This is not Archify on a git graph.
- v0 (or Bolt.new) scaffolds the first screens from the same spec.
- A human decides what gets a repo. Cursor and Claude Code start after this, not instead of it.