DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to draw the real data model from a Prisma schema with Vibex

Turn a Prisma schema into a validated ERD that shows the tables that actually ship.

Who it is forA developer joining a project or reviewing a database change who needs an accurate map of tables and relations.

The problemExisting diagrams in wikis or whiteboards go stale, and nobody is sure which tables join which.

The outcomeA validated ERD spec and a standalone HTML viewer showing tables, PK/FK badges, and cardinality taken from the schema.

What you need first

  • Node.js and npx, for the npx commands in the README
  • A Prisma schema, OpenAPI document, or GraphQL SDL file in the project, or source code the tool can read
  • Claude Code or Codex if you want to use vibeX as an agent skill

Steps

  1. vibex import prisma prisma/schema.prisma docs/db.erd.json
  2. vibex validate docs/db.erd.json
  3. vibex render docs/db.erd.json --open

Prompt for your agent

In the repo <repo path>, import prisma/schema.prisma into docs/db.erd.json with vibeX, validate it, and render docs/db.erd.html. Report the table count and any validation errors. Verify that every foreign key in the schema appears as a relation in the ERD.

Caveat. The ERD is generated from the Prisma schema, so it reflects what the schema declares, not what the database holds at runtime.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page