data-modeling

Transform business requirements into normalized data models for PostgreSQL or SQLite.

Updated Mar 18, 2025
One-click install
npx skills add https://github.com/zzoohub/mealio --skill data-modeling-zzoohub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-modeling
Source: https://github.com/zzoohub/mealio/tree/main/.claude/skills/data-modeling
Command: npx skills add https://github.com/zzoohub/mealio --skill data-modeling-zzoohub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform business requirements into logical data models, turning ambiguous needs into structured entities and their relationships.

Core Features & Use Cases

  • Discover entities from requirements
  • Define relationships and cardinality
  • Normalize data models and document decisions
  • Prepare for implementation with database skills (PostgreSQL or SQLite)

Quick Start

Provide a normalized data model describing entities and relationships from the given requirements to prepare for implementation with the database skill.

Frequently Asked Questions about data-modeling

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

FAQPage Schema
How do I turn business requirements into a normalized data model?

To turn business requirements into a normalized data model, you extract entities from the requirements, map their relationships and cardinality, and apply normalization decisions to produce a structured, scalable architecture ready for database implementation.

What is the best way to extract entities and map relationships for database design?

The best way to extract entities and map relationships for database design is to analyze the requirements to identify key objects, define their cardinality, and document the normalization decisions to ensure a clean, logical ER diagram.

Does this data modeling approach support PostgreSQL and SQLite implementation?

Yes, this data modeling approach explicitly supports PostgreSQL and SQLite implementation. It prepares normalized logical models and architecture documentation to ensure seamless handoff to your specific database environment.

When do I need to normalize a data model before database architecture setup?

You need to normalize a data model before database architecture setup when you have ambiguous business requirements. Normalization structures entities and relationships, reducing redundancy and preparing the architecture for scalable PostgreSQL or SQLite implementation.

Can I generate an ER diagram from ambiguous project requirements?

Yes, you can generate an ER diagram from ambiguous project requirements. The process transforms vague needs into structured entities, defines relationship cardinality, and documents architecture decisions to create a clear, normalized data model.