skills.rest
jonnathan-ls
jonnathan-lsCOMMUNITY
Explore all skills by this author →
𝕏@JonnathanLSGitHub

database-design

Design relational database schemas with normalization, primary keys, and indexing.

Updated Feb 19, 2026
Search Tags:#design#indexing#database#migrations#schema#orm#normalization
One-click install
npx skills add https://github.com/jonnathan-ls/ai-context-kit --skill database-design-jonnathan-ls
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/jonnathan-ls/ai-context-kit/tree/main/skills/database-design
Command: npx skills add https://github.com/jonnathan-ls/ai-context-kit --skill database-design-jonnathan-ls

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Designing scalable, maintainable databases without copying SQL patterns, ensuring robust schemas that scale with business needs.

Core Features & Use Cases

  • Normalization guidance: when to normalize versus denormalize, including PK selection and timestamp strategy.
  • Relationship modeling: one-to-many, many-to-many with join tables, and clear foreign key behaviors.
  • Use Case: plan a product catalog schema with migrations and ORM alignment for a growing app.

Quick Start

Draft a schema plan by listing entities, their fields, keys, relationships, and timestamps for your target domain, then align with ORM usage and migrations.

Frequently Asked Questions about database-design

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

FAQPage Schema
How do I design a scalable database schema for a growing application?▼

Design scalable database schemas by applying principled normalization, explicit primary key selection, and consistent timestamp fields. Define relationship types and foreign key delete behaviors to ensure the structure scales with business needs.

When should I normalize versus denormalize tables in PostgreSQL?▼

Normalize relational database tables to ensure data integrity and reduce redundancy, and denormalize selectively when read performance demands it. Apply clear primary keys and explicit foreign key behaviors to govern the relationship structure.

Can I use this schema design approach with ORM migrations?▼

Yes, the schema design approach aligns with ORM integration and database migrations. You can draft a schema plan listing entities, fields, keys, and relationships, then map those definitions directly to ORM usage and migration scripts.

What's the best way to model one-to-many and many-to-many relationships in MySQL?▼

Model one-to-many relationships using explicit foreign keys with defined delete behaviors, and model many-to-many relationships using dedicated join tables. Enforce clear primary keys on all tables to maintain referential integrity.

What are the limitations of relying on ORM auto-migrations for serverless database design?▼

ORM auto-migrations can generate schemas lacking principled normalization, indexing strategies, and explicit foreign key delete behaviors. Manual schema planning is required to enforce performance tuning and serverless optimization constraints.

Related Skills

Explore More Software Engineering Skills→
SSiertsemaSSiertsema

conceptual-data-modeling

Define domain entities, relationships, and business rules in plain language.

Community
Intermediate
jabrenajabrena
423

513-frameworks-micronaut-db-migrations-flyway

Manage Flyway database migrations in Micronaut applications.

Community
Advanced
amurataamurata
6

sql-optimization-patterns

Analyze SQL execution plans and apply indexing and query rewriting techniques.

Community
Advanced
miles990miles990
20

data-design

Guide relational and NoSQL database schema design with normalization and pipeline patterns.

Community
Advanced