Database Modelling

Design database schemas with entity-relationship modeling and normalization principles.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ftnilsson/agent-cli --skill database-modelling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Database Modelling
Source: https://github.com/ftnilsson/agent-cli/tree/main/backend/skills/02-database-modelling
Command: npx skills add https://github.com/ftnilsson/agent-cli --skill database-modelling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design effective database schemas that are performant, maintainable, and adaptable to future needs, regardless of the database technology used.

Core Features & Use Cases

  • Schema Design: Guides you through identifying entities, attributes, and relationships.
  • Normalization & Denormalization: Advises on balancing data integrity with query performance.
  • Indexing Strategies: Recommends optimal index creation for faster queries.
  • Schema Evolution: Provides patterns for safe and backward-compatible database migrations.
  • Use Case: When starting a new project that requires data storage, use this Skill to design a normalized schema that minimizes redundancy and ensures data consistency.

Quick Start

Design a normalized database schema for a blog application with users, posts, and comments.

Frequently Asked Questions about Database Modelling

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

FAQPage Schema
How do I design a database schema that minimizes redundancy and ensures data consistency?

Database schema design balances normalization principles to minimize redundancy while maintaining query performance. It guides you through identifying entities, attributes, and relationships to ensure robust data consistency across both relational and document stores.

What is the best way to plan database migrations without breaking backward compatibility?

Safe database migrations use schema evolution patterns to ensure backward compatibility and data integrity. Applying these techniques allows you to safely evolve your schema without disrupting existing application functionality or losing data.

How do I optimize SQL query performance with indexing strategies?

Optimize SQL query performance by applying targeted indexing strategies to your database schema. This involves recommending optimal index creation patterns to accelerate data retrieval operations while maintaining overall query efficiency.

Does this database schema design approach work for document stores as well as relational databases?

Yes, this schema design approach works for document stores and relational databases by providing comprehensive modeling guidance across both paradigms. It addresses entity-relationship modeling and data integrity challenges regardless of the underlying database technology.

When should I use denormalization instead of normalization in my database schema?

Use denormalization instead of normalization when query performance requires prioritizing over strict data integrity. This approach advises on balancing these principles to optimize read-heavy operations while managing acceptable data redundancy.

How do I model entity relationships for a new application database?

Model entity relationships for a new application database by using entity-relationship modeling to identify core entities, attributes, and their connections. This establishes a normalized schema foundation ensuring data consistency and supporting future schema evolution.