database-design

Name: database-design
Availability: InStock
Author: thgterto

Designs the structure of a database, including tables, columns, and relationships.

Updated Jan 3, 2026

Search Tags:#design #database #migrations #schema #indexes #normalization #relationships

Ready to run

npx skills add https://github.com/thgterto/Gerenciador-de-estoque --skill database-design-thgterto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/thgterto/Gerenciador-de-estoque/tree/main/.agent/skills/database-design
Command: npx skills add https://github.com/thgterto/Gerenciador-de-estoque --skill database-design-thgterto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Database design decisions often slow teams when choosing normalization levels, keys, and indexing. This guide provides structured principles to make these choices fast, consistent, and scalable.

Core Features & Use Cases

Normalization guidance: when to normalize vs denormalize to balance data integrity and performance.
Key and relationship modeling: primary keys, foreign keys, and relationship types with practical patterns.
Indexing and migrations: recommended indexing strategies and safe migration practices in evolving schemas.
Use case: In a new web app, apply these principles to craft a robust schema, define PKs/FKs, and plan indexes to support efficient queries.

Quick Start

Draft a normalized schema with clear primary keys and an indexing strategy for your project.

Frequently Asked Questions about database-design

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

FAQPage Schema

What's the best way to design a database schema for a scalable web app?▼

To design a normalized database schema, structure your relational models by grouping data to maintain integrity, define clear primary and foreign keys, and establish an indexing strategy to support efficient queries.

How do I decide when to normalize or denormalize a relational database?▼

Decide whether to normalize or denormalize by balancing data integrity against read performance. Normalize for consistency and clear relationships; denormalize when query speed demands it.

How do I plan safe database migrations for evolving schemas?▼

Plan safe database migrations by applying structured principles for evolving schemas, ensuring relationship types, keys, and indexing strategies remain consistent without disrupting existing relational models.

What indexing strategy should I use for high-performance database queries?▼

An effective indexing strategy for high-performance queries involves defining indexes based on your relationship types and primary keys, ensuring efficient data retrieval across small to large data sets.

Can I apply these database design principles to large data sets?▼

Yes, these database design principles apply across small to large data sets, providing structured guidance for maintainable schemas, efficient indexing, and robust relational models at any scale.