skills.rest
bernakilljos
bernakilljosCOMMUNITY
Explore all skills by this author →
GitHub

erdai-logical-model

Identify core entities, identifiers, and relationships for ERDAI logical data models.

Updated Aug 23, 2026
Search Tags:#documentation#data-modeling#erd#entity-relationship#model-review#domain-dictionary
One-click install
npx skills add https://github.com/bernakilljos/ERDAI --skill erdai-logical-model
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: erdai-logical-model
Source: https://github.com/bernakilljos/ERDAI/tree/main/.claude/skills/erdai-logical-model
Command: npx skills add https://github.com/bernakilljos/ERDAI --skill erdai-logical-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams build or refine the ERDAI logical data model, covering entities, identifiers, relationships, and the domain dictionary to ensure a consistent data backbone.

Core Features & Use Cases

  • Identify core entities, relationships, and candidate keys (PKs) needed for the ERD.
  • Define business keys and identifier strategy, aligning with data governance.
  • Update domain dictionary and terminology to reflect domain concepts.
  • Produce an up-to-date logical ERD and related documentation for downstream teams.

Quick Start

Identify core entities and relationships in the current project domain and update the logical ERD documentation accordingly.

Frequently Asked Questions about erdai-logical-model

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

FAQPage Schema
How do I document entities and relationships for a logical data model?▼

To document a logical data model, you identify core entities, business keys, and relationships, then define dictionary terms and constraint rules to produce an ERD-ready output with change tracking.

What is a domain dictionary in data modeling and when do I need one?▼

A domain dictionary in data modeling standardizes terminology to reflect domain concepts. You need it to ensure consistent data backbone governance and align business keys with identifier strategy across projects.

How do I define business keys and identifier strategy for an ERD?▼

Defining business keys and identifier strategy involves identifying candidate primary keys and aligning them with data governance rules to support consistent logical modeling and produce an up-to-date ERD.

Can I use this approach to update documentation for existing logical data models?▼

Yes, you can refine existing logical data model documentation by identifying core entities and relationships, updating the domain dictionary, and producing an actionable output with a plan for documentation updates.

What is the best way to maintain consistency across data modeling projects?▼

Maintaining consistency across data modeling projects requires defining constraint rules, business keys, and a domain dictionary to support consistent governance and produce an ERD-ready output with change tracking.

Do I need prior data governance rules to define a logical data model?▼

No, you can define data governance rules during the logical data modeling process by establishing business keys, dictionary terms, and constraint rules to support consistent modeling across projects.

Related Skills

Explore More Data & Analytics Skills→
TonyQ-AITonyQ-AI
9

domain-modeling

Extract core business concepts, entity relationships, and domain rules from requirement specifications.

Community
Intermediate
KaranKathur06KaranKathur06

data-modeling

Design data models with ERD notation, data dictionaries, and conceptual/logical/physical artifacts.

Community
Intermediate
serac-labsserac-labs
77

data-policies

Define and enforce ServiceNow data policies and dictionary rules.

Official
Advanced
darsoohoodarsoohoo

recipe-reverse-engineer

Generate PRD and Design Docs from an existing codebase.

Community
Advanced