entity-relationship-modeling

Translate entity-relationship models into relational database schemas with constraints.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill entity-relationship-modeling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: entity-relationship-modeling
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/entity-relationship-modeling
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill entity-relationship-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Entity-relationship modeling turns unclear conceptual requirements into correct, constraint-backed database tables that are safe to migrate and resilient to real-world data.

Core Features & Use Cases

  • ER-to-SQL translation: Convert ER notation into concrete relational structures with primary keys, foreign keys, junction tables, and constraints.
  • Normalization & denormalization guidance: Choose appropriate normal forms for OLTP correctness and decide when denormalization is justified for performance.
  • Temporal modeling & inheritance mapping: Implement SCD strategies and inheritance patterns (STI/class-table/concrete-table) without breaking integrity.
  • Quality verification checklist: Validate identity, referential actions, indexing expectations, and anti-pattern avoidance (EAV, polymorphic associations, mega-tables).

Quick Start

Use entity-relationship-modeling to translate your ER diagram for an Orders system into a PostgreSQL schema with correct keys, foreign keys, constraints, and indexing assumptions.

Frequently Asked Questions about entity-relationship-modeling

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

FAQPage Schema
How do I translate an entity-relationship diagram into a SQL schema with correct foreign key constraints?

ER-to-SQL translation converts ER notation into concrete relational structures with primary keys, foreign keys, junction tables, and constraints for table creation and migration planning.

What is the best way to normalize a database schema through BCNF without breaking referential integrity?

Normalization through BCNF decomposes tables to eliminate functional dependencies while maintaining referential integrity via explicit foreign key constraints and consistent ON DELETE behavior specifications.

How do I model many-to-many relationships using junction tables in a relational database?

Junction tables resolve many-to-many relationships in relational database schema design by referencing the primary keys of both parent tables, establishing foreign key constraints with defined ON DELETE actions.

When should I avoid EAV and polymorphic associations when designing a database schema?

Avoid EAV and polymorphic associations during schema review to prevent anti-patterns; instead, use proper entity-relationship modeling with explicit columns, foreign key constraints, and normalized table structures for data integrity.

How do I implement temporal SCD modeling and inheritance mapping when creating database tables?

Temporal SCD modeling and inheritance mapping use class-table or concrete-table patterns to track historical data changes and entity hierarchies while maintaining database integrity through proper constraint specification.

Does entity-relationship modeling support schema migration planning for PostgreSQL databases?

Entity-relationship modeling produces relational database schema designs suitable for table creation and schema migration planning across SQL databases like PostgreSQL, including consistent constraint specification and indexing expectations.