database-design

Guide schema design, indexing strategies, and ORM selection for database projects.

7|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skeletorflet/opencode-kit --skill database-design-skeletorflet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/skeletorflet/opencode-kit/tree/main/.opencode/skills/database-design
Command: npx skills add https://github.com/skeletorflet/opencode-kit --skill database-design-skeletorflet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Database design decisions influence scalability, data integrity, and long-term maintainability; this guide helps engineers make consistent choices across schema design, keys, and migrations.

Core Features & Use Cases

  • Guidance on normalization vs denormalization for relational schemas, including when to apply each pattern.
  • Best practices for primary keys, timestamps, foreign keys, and relationship modeling.
  • A practical decision framework for ORM selection, indexing strategies, and deployment models (including serverless databases).

Quick Start

Review the decision checklist and apply normalization, indexing, and ORM guidance to your next database design task.

Frequently Asked Questions about database-design

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

FAQPage Schema
How do I decide between database normalization and denormalization for my schema design?

Schema design uses normalization to ensure data integrity and denormalization to optimize read performance. Apply normalization for strict consistency, and denormalize when read scalability demands it. A decision checklist guides when to use each pattern.

What are the best practices for defining primary keys and timestamps in relational databases?

Primary keys and timestamps require consistent conventions for reliable relationship modeling. Primary keys must uniquely identify rows, while timestamps track record creation and updates. Following these conventions ensures data integrity across migrations and deployments.

How do I choose an ORM and indexing strategy for a serverless database?

ORM selection and indexing strategies for serverless databases depend on query patterns and scale constraints. Evaluate ORMs based on migration support, and apply indexing to optimize frequent queries without exceeding serverless connection limits.

What is the safest way to execute database migrations across deployment teams?

Safe database migrations across teams require strict deployment considerations and timestamp conventions. Execute migrations incremently, ensuring backward compatibility and avoiding locks. A decision framework provides safe migration recommendations to prevent downtime.

When do I need to apply relationship modeling and foreign keys in my database schema?

Relationship modeling and foreign keys are needed to enforce referential integrity between tables in a relational schema. Apply foreign keys when tables depend on each other, ensuring valid relationships and preventing orphaned records during data migrations.