data-model-design

Plans modular app data models and migrations with UUID keys and JSONB usage.

1|2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/matchojecki/logistiko-celny --skill data-model-design-matchojecki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-model-design
Source: https://github.com/matchojecki/logistiko-celny/tree/main/packages/create-app/agentic/shared/ai/skills/data-model-design
Command: npx skills add https://github.com/matchojecki/logistiko-celny --skill data-model-design-matchojecki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design entities, relationships, and manage the migration lifecycle following Open Mercato conventions.

Core Features & Use Cases

  • Entity design templates and standards to enforce consistent schemas
  • Migration lifecycle guidance including generation, validation, and rollout planning
  • Cross-module references and relationship pattern guidance (1:N, N:M with junction tables)
  • Real-world use case: design a product catalog with Product, Category, and Inventory entities and a migration plan

Quick Start

Design a starter data model plan for a new module including entities, keys, and a basic migration outline.

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 a data model with UUID primary keys and tenant isolation in TypeScript?▼

Data model design for modular TypeScript applications uses UUID primary keys alongside organization_id and tenant_id columns for tenant isolation. This approach enforces consistent schemas and prevents cross-module ORM constraints.

What's the best way to plan database migrations for a modular application?▼

Planning database migrations for modular applications involves guiding the generation, validation, and rollout lifecycle. This structured migration planning ensures safe schema evolution across independent application modules.

How do I manage cross-module references without breaking modular architecture?▼

Managing cross-module references without breaking modular architecture requires non-cross-module ORM constraints. Data model design uses references and junction tables for 1:N and N:M relationships to maintain strict module boundaries.

When should I use JSONB columns in a data model design?▼

JSONB columns in data model design are used to store flexible, semi-structured data within entities. This approach allows schema evolution without rigid migrations while maintaining core relational integrity.

Does this data model design approach work for multi-tenant SaaS applications?▼

This data model design approach explicitly works for multi-tenant SaaS applications by enforcing organization_id and tenant_id guidelines. It ensures data isolation and consistent schema management across modular application components.

Why does my ORM constraint fail when querying across different application modules?▼

ORM constraints fail across application modules because this data model design imposes non-cross-module ORM restrictions. You must use cross-module references instead of direct ORM joins to maintain modular architecture boundaries.