skills.rest
ps-carvalho
ps-carvalhoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

database-design

Generate normalized database schemas with indexing and migration strategies.

Updated Feb 22, 2026
Search Tags:#design#performance#indexing#database#migrations#orm#normalization
One-click install
npx skills add https://github.com/ps-carvalho/cortex-agents --skill database-design-ps-carvalho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/ps-carvalho/cortex-agents/tree/main/.opencode/skills/database-design
Command: npx skills add https://github.com/ps-carvalho/cortex-agents --skill database-design-ps-carvalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database design often fails to scale or maintain data integrity, leading to slow queries and brittle architectures.

Core Features & Use Cases

  • Normalization guidance (1NF-3NF) to ensure data consistency across tables.
  • Indexing and performance patterns for read-heavy and write-heavy workloads.
  • ORM strategies and migration best practices to enable safe schema evolution.

Quick Start

Generate a normalized schema plan for a new app, including tables, keys, and indexes.

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 normalized database schema for a scalable application?▼

To design a normalized database schema, apply 1NF through 3NF rules to ensure data consistency across tables. This process defines tables, primary keys, and indexes, creating a robust foundation that maintains data integrity and optimizes query performance for scalable apps.

What is the best way to handle database migrations and ORM mapping?▼

The best way to handle database migrations and ORM mapping involves applying migration best practices alongside ORM strategies. This approach enables safe schema evolution, ensuring your relational or document store schema scales without brittle architecture or data loss.

When should I use NoSQL document stores versus relational SQL databases?▼

Choose between relational SQL and NoSQL document stores by evaluating your data structure and workload. Relational databases enforce normalization and data integrity, while NoSQL suits flexible schemas, with indexing patterns guiding performance for read-heavy or write-heavy workloads.

How do I optimize database indexing for read-heavy and write-heavy workloads?▼

Optimize database indexing by applying specific performance patterns tailored to your workload. For read-heavy workloads, use indexes to accelerate queries, while write-heavy workloads require careful index management to prevent insertion bottlenecks and maintain overall performance.

Why does my database design fail to scale and maintain data integrity?▼

Database design fails to scale and maintain data integrity when it lacks proper normalization and indexing. Without applying 1NF-3NF rules and ORM migration strategies, schemas become brittle, leading to slow queries and poor data consistency across tables.

Related Skills

Explore More Software Engineering Skills→
musujmusuj

phase-1-schema

Define project terminology, entities, relationships, and data structures.

Community
Intermediate
UnicornUnicorn

data-migration-agent

Plan and execute data migrations across databases with validation and rollback.

Official
Advanced
ViewWayViewWay

SQL

Design schemas, write portable SQL, and coordinate migrations across PostgreSQL, MySQL, SQLite, and SQL Server.

Community
Advanced
rsmdtrsmdt
381

data-modeling

Design database schemas from domain requirements with ER modeling and normalization.

Community
Advanced