Data Modelling Skill

Design relational database schemas with universal data model patterns and SQL DDL.

75|8|Updated Dec 20, 2023
One-click install
npx skills add https://github.com/flowkraft/datapallas --skill data-modelling-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Data Modelling Skill
Source: https://github.com/flowkraft/datapallas/tree/main/asbl/src/main/external-resources/db-template/_apps/flowkraft/_ai-hub/.skills/data-modelling
Command: npx skills add https://github.com/flowkraft/datapallas --skill data-modelling-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design database schemas that reflect real business entities and relationships without unnecessary complexity, reducing rework and modeling mistakes.

Core Features & Use Cases

  • Universal data model patterns: Leverages battle-tested patterns (e.g., Party, Product, Order/Transaction, Work Effort, Accounting) as a starting point.
  • Simple-to-complex progression: Recommends the simplest viable schema variant first, adding temporal/versioning complexity only when business rules require it.
  • OLTP vs OLAP schema choices: Translates requirements into either normalized (3NF) transactional schemas or dimensional (star/snowflake) analytical schemas.
  • DDL-ready outputs: Produces concrete table/column/relationship designs and CREATE TABLE DDL tailored to common SQL dialects.

Quick Start

Describe your business domain and key entities, then ask for a schema that starts simple and includes the necessary joins and DDL for your database vendor.

Frequently Asked Questions about Data Modelling Skill

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

FAQPage Schema
How do I design a normalized database schema for OLTP vs OLAP?

Database schema design for OLTP uses normalized 3NF structures for transactions, while OLAP dimensional modeling applies star or snowflake schemas for analytical queries. This Skill maps your requirements to the appropriate schema type and generates vendor-specific SQL DDL.

What are universal data model patterns for database schema design?

Universal data model patterns are proven structural templates like Party, Product, Order, and Accounting that map real business entities to relational tables. This Skill uses them to design clean schemas reflecting business logic without unnecessary complexity.

How do I generate SQL DDL from a database schema design?

You generate SQL DDL by defining your business domain and key entities. This Skill outputs concrete table, column, and relationship designs, translating them directly into CREATE TABLE statements tailored to your specific SQL dialect.

When should I add temporal or versioning complexity to a database schema?

Add temporal or versioning complexity to a database schema only when business rules explicitly require tracking historical changes. This Skill recommends the simplest viable schema variant first, adding complexity solely when necessary to preserve data integrity.

What is the best way to model pricing and ordering concepts in a relational database?

Model pricing and ordering concepts using universal data model patterns that cleanly represent entity roles and transaction structures. This Skill designs these mapped schemas while explaining trade-offs between normalization and query performance.