data-model-design

Design data models, entities, and their relationships for software and database systems.

Updated May 31, 2026
One-click install
npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill data-model-design-zizzfizzix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-model-design
Source: https://github.com/zizzfizzix/agentic-engineering-framework/tree/main/core/ai/skills/data-model-design
Command: npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill data-model-design-zizzfizzix

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill aids in the design and planning of data models, entities, and their relationships, streamlining the process and reducing the risk of common design pitfalls.

Core Features & Use Cases

  • Entity Design: Helps identify entities, fields, and relationships.
  • Field Types: Provides guidance on choosing appropriate field types.
  • Relationship Patterns: Offers patterns for one-to-one, one-to-many, many-to-many, and self-referencing relationships.
  • Cross-boundary References: Encourages best practices for referencing entities across module/service boundaries.
  • Migration Lifecycle: Outlines rules for schema changes and migrations.
  • ORM Cheatsheet: Includes ORM-specific guidance for implementing design decisions.
  • Anti-patterns and Rules: Lists common anti-patterns and rules for maintaining a robust data model.
  • Use Case: Ideal for software engineers and database designers working on complex systems, to ensure data models are well-structured and maintainable.

Quick Start

Use the data-model-design skill to design a new entity for your application, ensuring it adheres to best practices for entity relationships and field types.

Frequently Asked Questions about data-model-design

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

FAQPage Schema
How do I design data models and entity relationships for a new application?

Data model design involves identifying entities, selecting field types, and defining relationship patterns. This process streamlines entity creation and reduces common design pitfalls like poor cross-boundary references.

What are the best patterns for one-to-many and many-to-many relationships in database schema design?

Schema design provides specific patterns for one-to-one, one-to-many, many-to-many, and self-referencing relationships. These patterns ensure entities are well-structured and maintainable across complex systems.

How do I handle cross-boundary references when designing entities for microservices?

Cross-boundary references require applying best practices for referencing entities across module or service boundaries. Proper data model design encourages rules that maintain robust relationships without tight coupling.

What common anti-patterns should I avoid during ORM entity design?

ORM entity design anti-patterns include improper field type selection and poorly structured relationship patterns. Following established data model rules prevents these issues and maintains a robust schema throughout the migration lifecycle.

How do I manage schema changes and migration lifecycles for existing data models?

Schema migration lifecycle management outlines specific rules for executing schema changes on existing data models. This ensures structural modifications adhere to database design principles without breaking entity relationships.