05-erd-diagrams

Generate Mermaid ERD diagrams for data modeling documentation.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/prashsub/vibe_coding_lakehouse_starter_repo --skill 05-erd-diagrams-prashsub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 05-erd-diagrams
Source: https://github.com/prashsub/vibe_coding_lakehouse_starter_repo/tree/main/data_product_accelerator/skills/gold/design-workers/05-erd-diagrams
Command: npx skills add https://github.com/prashsub/vibe_coding_lakehouse_starter_repo --skill 05-erd-diagrams-prashsub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides standardized patterns and best practices for creating clean, maintainable, and professional Mermaid ERD diagrams to document data models.

Core Features & Use Cases

  • Standardized ERD Creation: Offers clear guidelines for organizing ERDs (master, domain-specific, summary) based on model complexity.
  • Syntax and Formatting: Enforces consistent syntax, indentation, and relationship labeling for readability.
  • Use Case: When documenting a new Gold layer data model with over 20 tables, use this Skill to generate domain-specific ERDs for focused views and a summary ERD for a high-level overview.

Quick Start

Use the 05-erd-diagrams skill to create a master ERD for the gold layer data model.

Frequently Asked Questions about 05-erd-diagrams

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Mermaid ERD diagrams for data modeling documentation?

Mermaid ERD diagrams are generated using standardized syntax, indentation, and relationship labeling patterns to document data models. This approach creates clean, professional diagrams for maintaining complex data architectures.

What is the best way to document a Gold layer data model with many tables?

For a Gold layer data model with 20+ tables, generate domain-specific ERDs for focused views and a summary ERD for high-level overviews. This organization strategy maintains readability and enforces cross-domain reference patterns.

When do I need a summary ERD versus a master ERD?

Use a summary ERD for large models with 20+ tables to provide a high-level overview, and a master ERD to map the complete data model. Domain-specific ERDs provide focused views of individual business areas within the Gold layer.

How do I structure relationships and syntax in Mermaid ERD diagrams?

Structure Mermaid ERD diagram syntax by applying consistent indentation, standardized relationship patterns, and clear relationship labeling. This enforces readability and maintains professional diagram formatting across data modeling documentation.

Can I create domain-specific ERDs for focused views of my data model?

Yes, you can create domain-specific ERDs to generate focused views of individual areas within your data model. This approach enforces cross-domain reference patterns and is particularly useful when documenting complex Gold layer architectures.

Are there limitations when generating ERD diagrams for very large data models?

For large data models with 20+ tables, generating a single master ERD becomes difficult to read. This limitation is mitigated by generating summary ERDs for high-level overviews and domain-specific ERDs to maintain documentation clarity.