Prompt library

ERD Prompts

ERD prompts work best when they name the entities, relationships, and key attributes or constraints. These examples help you generate a clean first-pass schema diagram before you finalize table details.

Each prompt here is built for AI-native technical diagrams in AIDrawIO. Start from plain English, get draw.io-compatible output, then keep editing as XML or export SVG and PNG.

Open app Browse free tools

Copyable prompt blocks

Grab a proven prompt quickly instead of composing from scratch every time.

Refinement-ready

Each prompt includes a follow-up so you can add boundaries, detail, and review context.

Editable outputs

Generated diagrams stay compatible with draw.io workflows instead of locking you into images.

Copy and generate

Copyable prompts for erd prompts

Use one prompt as-is, or combine it with the follow-up prompt to add labels, constraints, security detail, or failure handling.

Prompt 1

Ecommerce schema

Prompt

Create an ERD for an ecommerce application with users, addresses, products, categories, carts, cart_items, orders, order_items, payments, and shipments. Show primary keys, foreign keys, and one-to-many relationships.

Why this prompt works

It gives the model a realistic set of commerce entities and tells it to include the relationship details that matter in a real ERD.

Follow-up prompt

Add product variants, inventory per warehouse, and coupon tables with the relevant relationships.

Prompt 2

B2B SaaS multi-tenant schema

Prompt

Generate an entity relationship diagram for a multi-tenant SaaS app with organizations, users, memberships, roles, workspaces, projects, tasks, comments, audit_logs, and API keys. Mark tenant boundary fields and main ownership relationships.

Why this prompt works

It explicitly calls out tenancy and access structure, which are usually the core complexity in SaaS schema diagrams.

Follow-up prompt

Add billing entities such as subscriptions, invoices, usage records, and payment methods.

Prompt 3

Marketplace data model

Prompt

Draw an ERD for a marketplace platform with buyers, sellers, listings, categories, orders, payouts, disputes, reviews, and messages. Include many-to-many relationships where needed using junction tables.

Why this prompt works

It tells the model to handle marketplace-specific complexity and explicitly mentions junction tables for many-to-many cases.

Follow-up prompt

Add fulfillment, return requests, and tax reporting entities.

How to use these prompts

From prompt to editable diagram

Pick a base prompt

Choose the closest prompt for your architecture, workflow, or schema.

Generate in AIDrawIO

Paste it into the app and create the first structured draft fast.

Refine with follow-up

Add more scope like failure paths, zones, labels, or compliance detail.

Export and share

Keep draw.io-compatible XML or export SVG and PNG for docs and review.

Related tools

Jump into a specialized generator when you know the exact diagram category.

ERD Generator

AI entity-relationship diagrams

UML Diagram Generator

AI UML class, state, and activity diagrams

Data Flow Diagram Generator

AI data flow diagrams (DFD)

More prompt pages

Use adjacent prompt libraries when your diagram crosses categories.

AWS Architecture Diagram Prompts

These prompts help you generate AWS diagrams faster by naming the key services, traffic paths, and boundaries clearly. Start with one, then use follow-up prompts to add subnets, security controls, or scaling detail.

System Design Diagram Prompts

Use these prompts when you need a system design diagram quickly for interview prep, architecture reviews, or internal docs. Each one names the major components, scaling path, and data flow so the diagram is easy to inspect and refine.

Sequence Diagram Prompts

Sequence diagrams are easiest to generate when the prompt names actors, the order of requests, and any alternate or failure paths. These prompts give you a clean base for auth flows, API interactions, and service-to-service messaging.

Kubernetes Diagram Prompts

Kubernetes diagrams become more useful when prompts mention namespaces, ingress, services, deployments, pods, and storage explicitly. These prompts help you produce clean cluster diagrams for docs, reviews, and onboarding.

FAQ

Common questions about erd prompts

What makes a good ERD prompt?

A good ERD prompt names the main entities, the relationships between them, and whether you want keys, junction tables, or important constraints shown.

Can AI generate database schema diagrams?

Yes. AIDrawIO can generate ERD-style diagrams from plain-English schema descriptions.

Should I include columns and keys in the prompt?

Include them when you need a more physical ERD. For a conceptual ERD, entities and relationships may be enough for the first draft.