ring:pre-dev-data-model

Model abstract data entities, ownership, and relationships before selecting database technologies.

4|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-data-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ring:pre-dev-data-model
Source: https://github.com/LerianStudio/ring-for-opencode/tree/main/assets/skill/pre-dev-data-model
Command: npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-data-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams model abstract data entities, ownership, and relationships before selecting any database technology, ensuring consistent design and scalable data governance across services.

Core Features & Use Cases

  • Abstract data modeling: define entities, attributes, and relationships without tying to a specific database.
  • Ownership & lifecycle planning: assign data ownership, creation, updates, deletion, and archival rules.
  • Gate-aligned validation: aligns with Gate 5 requirements (entity completeness, data ownership, access patterns, and cross-component consistency).
  • Use cases: supports multi-service architectures, API design alignment, and data governance initiatives.

Quick Start

Review the Foundational Principle and Mandatory Workflow in the Skill notes, then draft a technology-agnostic data model that identifies entities, key attributes, identifiers, and ownership per TRD components.

Frequently Asked Questions about ring:pre-dev-data-model

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

FAQPage Schema
Why define abstract data structures before selecting a database technology?

Defining abstract data structures first ensures consistent design and scalable data governance across services by documenting entities and relationships without tying them to specific database implementations.

How do I model data entities and ownership for multi-service architectures?

You model data entities and ownership by documenting entities, attributes, relationships, and lifecycle rules in a technology-agnostic way, ensuring clear ownership boundaries across multi-service architectures before storage selection.

Can I use this approach to align data governance with API design workflows?

Yes, this approach aligns data governance with API design workflows by defining abstract data models, access patterns, and cross-component consistency, ensuring data structures support governance initiatives effectively.

What is technology-agnostic data modeling and when do I need it?

Technology-agnostic data modeling is the process of defining data entities, attributes, and relationships independently of any specific database technology. You need it for data-heavy projects to ensure scalable and consistent data governance.

How do I document data ownership and lifecycle rules for data governance?

You document data ownership and lifecycle rules by assigning responsibilities for data creation, updates, deletion, and archival within an abstract model, ensuring clear accountability for data governance initiatives.

Does abstract data modeling support cross-component consistency validation?

Yes, abstract data modeling supports cross-component consistency validation by aligning entity completeness, data ownership, and access patterns with Gate 5 requirements, ensuring consistent design across services.