EF Core D2 Database Diagram Generator

When to Use

Use this skill when the user wants to generate a database / ERD diagram from an Entity Framework Core codebase.

Typical requests:

• Generate a D2 database diagram from EF Core entities.
• Visualize tables, columns, primary keys, foreign keys and relationships.
• Analyze DbContext, DbSet<T>, IEntityTypeConfiguration<T>, Fluent API and migrations.
• Produce a .d2 file renderable to SVG/PNG with the d2 CLI.
• Document the database model of an ASP.NET Core / .NET project.

Goal

Create a readable D2 entity-relationship diagram that reflects the actual EF Core persistence model, not only the raw C# class shape.

The diagram must prioritize:

1. Database tables and relationships.
2. Primary keys, foreign keys, required/optional columns.
3. Owned types and value objects.
4. Many-to-many relationships and join tables.
5. Indexes, unique constraints and table names.
6. EF Core conventions only when explicit mapping is absent.

Output is .d2 source code. It can be rendered to SVG or PNG via the d2 CLI.

Tools

• d2 CLI: render .d2 files to SVG/PNG.
  • d2 input.d2 output.svg
  • d2 --layout=elk input.d2 output.svg
• d2 fmt: format D2 files.
  • d2 fmt input.d2
• No MCP server is required. The skill generates D2 source code as text.

Recommended Workflow

1. Read the EF Core project structure.
2. Locate all DbContext classes.
3. Locate all DbSet<T> declarations.
4. Locate entity classes, owned types, enum types and value objects.
5. Read OnModelCreating and all IEntityTypeConfiguration<T> classes.
6. Read migrations when available to confirm table names, join tables, indexes and delete behaviors.
7. Build a normalized database model before writing D2.
8. Ask the mandatory diagram questionnaire before generation.
9. Generate the .d2 file using the database model, not raw class nesting.
10. Validate D2 syntax with d2 fmt before delivery.
11. Render with d2 --layout=elk schema.d2 schema.svg when possible.
12. If regenerating, re-read EF Core mappings and migrations first.

Mandatory Questions Before Diagram Generation

Ask these questions for every new diagram and every regeneration unless the user already answered them in the same request.

1. Which DbContext should be diagrammed? (auto-detect/all/specific name)
2. Display columns? (all/key-only/none)
3. Display column types? (Yes/No)
4. Display nullable/required markers? (Yes/No)
5. Display indexes and unique constraints? (Yes/No)
6. Display enum values? (Yes/No)
7. Display owned types? (inline/separate/hide)
8. Display many-to-many join tables? (explicit/compact/hide)
9. Display audit/technical tables? (Yes/No)
10. Display migration-only tables not present as entities? (Yes/No)
11. Which grouping mode? (bounded-context/schema/namespace/flat)
12. Which layout engine? (elk/dagre/tala)
13. Which output format? (d2/svg/png)

Default values, when the user asks for a quick generation:

• DbContext: auto-detect
• Columns: key-only
• Column types: Yes
• Nullable markers: Yes
• Indexes: Yes
• Enums: No
• Owned types: inline
• Join tables: explicit
• Audit/technical tables: No
• Migration-only tables: Yes
• Grouping: bounded-context
• Layout: elk
• Output: d2

Reference Documents

Load these on demand when needed:

EF Core Extraction Rules

Source Priority

Use this priority order when sources disagree:

1. Latest applied migration / migration snapshot.
2. Fluent API configuration in OnModelCreating or IEntityTypeConfiguration<T>.
3. Data annotations.
4. EF Core conventions.
5. Raw C# class shape.

Required EF Core Concepts to Detect

Detect and represent:

• DbContext and DbSet<T>.
• Entity class names and actual table names from ToTable.
• Schema names from ToTable("Table", "schema").
• Primary keys from HasKey, [Key], conventions and migrations.

…