What is the primary benefit of modeling before database selection?

It prevents 'implementation-first' mistakes like inconsistent data structures, unclear data ownership, and schema conflicts that are costly to fix during the development phase.

When should I use the Pre-Dev Data Model skill?

Use it for 'Large Track' workflows (features expected to take 2+ days) that involve persistent storage and multiple entities with complex relationships.

How does it integrate with API designs?

It specifically looks for Gate 4 API standards to automatically suggest database field names, ensuring a 1:1 mapping between your API contracts and your internal data structures.

Does this skill generate SQL schemas or migrations?

No, this skill focuses on conceptual data modeling. It intentionally avoids database-specific details like SQL or ORM code to ensure the architectural design remains technology-agnostic.

Pre-Dev Data Modeling

Name: Pre-Dev Data Modeling
Author: luanrodrigues

byluanrodrigues

•

数据库管理

Models conceptual data structures, entity relationships, and ownership rules before technical implementation begins.

The Pre-Dev Data Model skill automates 'Gate 5' of the software development lifecycle, focusing on high-level data architecture for complex features. It guides developers through defining entities, attributes, and relationships while strictly maintaining database-agnosticism. By establishing a clear naming strategy—such as converting API camelCase to database snake_case—and defining data ownership early, this skill prevents schema conflicts and inconsistent data structures across services before a single line of SQL is written.

主要功能

01Conceptual entity-relationship modeling without technology lock-in

02Automated database field naming strategy and mapping from API designs

03Gate-based validation checklist to ensure data quality and consistency

04Comprehensive lifecycle management planning (soft deletes, archival, audit trails)

052 GitHub stars

06Component-based data ownership mapping to ensure architectural integrity

使用场景

01Ensuring naming consistency between frontend API contracts and backend storage

02Defining data ownership and access patterns in microservices architectures

03Architecting the persistent data layer for complex, multi-entity backend features

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add luanrodrigues/ia-frmwrk pre-dev-data-model

For use in Claude.ai and ChatGPT

主要功能

01Conceptual entity-relationship modeling without technology lock-in

02Automated database field naming strategy and mapping from API designs

03Gate-based validation checklist to ensure data quality and consistency

04Comprehensive lifecycle management planning (soft deletes, archival, audit trails)

052 GitHub stars

06Component-based data ownership mapping to ensure architectural integrity

使用场景

01Ensuring naming consistency between frontend API contracts and backend storage

02Defining data ownership and access patterns in microservices architectures

03Architecting the persistent data layer for complex, multi-entity backend features

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add luanrodrigues/ia-frmwrk pre-dev-data-model

For use in Claude.ai and ChatGPT