efcore-d2-db-diagram

Topics in the source

• EF Core D2 Database Diagram Generator
• When to Use
• Goal
• Tools
• Recommended Workflow
• Mandatory Questions Before Diagram Generation
• Reference Documents
• EF Core Extraction Rules

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 , IEntityTypeConfiguration , 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. 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. 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. 1. Read

This is an excerpt. Refer to the complete source and its current requirements.