data-modeling

Design database schemas with ER modeling, normalization, and migration planning.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill data-modeling-i2oland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-modeling
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/data-modeling
Command: npx skills add https://github.com/I2olanD/dotfiles --skill data-modeling-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing robust, scalable database schemas is hard; this Skill provides structured guidance for data modeling, normalization, and schema evolution to ensure maintainable architectures.

Core Features & Use Cases

  • Entity-relationship modeling guidance to capture domain concepts and lifecycles.
  • Normalization up to 3NF with practical denormalization tips for performance.
  • Migration planning and versioning strategies to safely evolve schemas.

Quick Start

Outline your domain entities and relationships, then draft a schema using the provided templates and guidelines to begin modeling.

Frequently Asked Questions about data-modeling

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

FAQPage Schema
How do I design a database schema for scalability and data integrity?

Designing robust database schemas involves entity-relationship modeling to capture domain concepts, normalization up to 3NF to ensure integrity, and practical denormalization tips to maintain performance as your data scales.

What is the best way to plan database migrations for evolving domains?

Planning database migrations involves applying schema versioning strategies to safely evolve data models. It enforces structured design rules to safely evolve schemas without disrupting existing domain logic or data integrity.

Can I use this data modeling guidance for NoSQL and hybrid stores?

Yes, this data modeling guidance is applicable to relational, NoSQL, and hybrid stores. It provides a reusable schema template and enforces structured design rules to help teams communicate data architecture decisions across different database architectures.

How do I normalize a database schema to 3NF without sacrificing performance?

Normalizing a database schema to 3NF ensures data integrity by reducing redundancy, while practical denormalization tips help maintain query performance. Structured ER modeling captures domain concepts first to balance normalization rules with performance requirements.

When should I use entity-relationship diagrams for database architecture?

Entity-relationship diagrams are used during database architecture to capture domain concepts and lifecycles. ER modeling provides structured guidance to ensure maintainable architectures and clearly communicate data architecture decisions across teams.

Does denormalization help with database schema performance?

Denormalization improves database schema performance by strategically reversing normalization rules. It provides practical denormalization tips to optimize query speed while maintaining the structural integrity established during initial ER modeling and schema design.