data-modeler

Generate conceptual and logical data models for full-stack MVPs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/apadern/.github_tailormade --skill data-modeler-apadern
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-modeler
Source: https://github.com/apadern/.github_tailormade/tree/main/skills/data-modeler
Command: npx skills add https://github.com/apadern/.github_tailormade --skill data-modeler-apadern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elabora un modelo de datos claro y completo para MVPs full-stack, evitando ambigüedades y retrabajo en fases posteriores.

Core Features & Use Cases

  • Genera catálogos de entidades, atributos y relaciones a alto nivel con mapeo a persistencia.
  • Describe dependencias entre módulos y produce un diagrama ER para visualización.
  • Caso de uso: un MVP de gestión de usuarios y expedientes genera entidades como Usuario, Expediente y DocumentoAdjunto con relaciones 1:N y reglas de persistencia.

Quick Start

Proporciona los requerimientos funcionales y pantallas del MVP para generar design/02_data_model.md.

Frequently Asked Questions about data-modeler

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

FAQPage Schema
How do I generate a data model for a full-stack MVP from functional requirements?

You generate a data model for a full-stack MVP by providing functional requirements and UI screens, which produces a comprehensive design document detailing entities, attributes, relationships, and persistence mappings.

What is included in a conceptual and logical data model for MVP database design?

A conceptual and logical data model for MVP database design includes entity catalogs, attributes, high-level relationships, module dependencies, persistence mappings, and an entity-relationship diagram for visualization.

Can I use functional requirements and UI screens to create an entity-relationship diagram?

Yes, you can use functional requirements and UI screens to create an entity-relationship diagram by defining entities and their relationships at a high level during the functional analysis and design phase.

Does this data modeling approach include low-level implementation details for database persistence?

No, this data modeling approach does not include low-level implementation details; it defines entities, relationships, and persistence mappings at a high level to avoid ambiguities and rework.

What is the best way to define module dependencies and persistence mappings for an MVP?

The best way to define module dependencies and persistence mappings for an MVP is generating a high-level logical data model from requirements and UI screens to clarify structure before implementation.