How do I install the Knowledge Data Modeling skill?

Run npx skillmds@latest add deankelly751/knowledge-data-modeling in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Knowledge Data Modeling safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Knowledge Data Modeling?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Knowledge Data Modeling free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Knowledge Data Modeling?

DeanKelly751 (@deankelly751) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Knowledge Data Modeling by deankelly751

Name: Knowledge Data Modeling
Author: DeanKelly751

Knowledge Data Modeling

Data modeling from conceptual to physical level. Covers entity relationship modeling, cardinality, inheritance strategies, and translating domain models to schemas. Use when starting new database designs or mapping domain concepts to tables.

DeanKelly751 Updated Sep 21, 2026

File contents

Data Modeling

Purpose

Systematic approach to translating domain concepts into database structures.

Modeling Levels

Level	Audience	Contains	Tools
Conceptual	Business stakeholders	Entities, relationships	Whiteboard, ER diagrams
Logical	Developers, architects	Attributes, keys, cardinality	ER diagrams, UML
Physical	DBAs, developers	Tables, columns, types, indexes	DDL, migration files

Relationship Patterns

Cardinality	Implementation
1:1	Foreign key with UNIQUE constraint, or same table
1:N	Foreign key on the "many" side
M:N	Junction/join table with composite key
Self-referential	Foreign key referencing same table

Inheritance Strategies

Strategy	When to use	Trade-off
Single table	Few subtypes, similar attributes	Sparse nulls
Table-per-type	Many attributes per subtype	Joins needed
Table-per-concrete	Subtypes rarely queried together	No shared table

Modeling Heuristics

Nouns → entities/tables
Verbs → relationships or junction tables
Adjectives → attributes or enum columns
"Has many" → 1:N foreign key
"Belongs to many" → M:N junction table

Related Skills

database/knowledge-schema-design — physical schema from the model
architecture/knowledge-ddd — domain model driving data model

Frequently asked questions