database-design

Design PostgreSQL schemas with relationships, constraints, indexes, and reversible migrations.

44|9|Updated May 7, 2026
One-click install
npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill database-design-omar-obando
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/database-design
Command: npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill database-design-omar-obando

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database design guidance for turning requirements into schemas that stay correct over time, remain performant under load, and avoid risky migrations.

Core Features & Use Cases

  • Normalization & Integrity Modeling: Choose normalization levels, model relationships cleanly, and enforce data integrity with constraints.
  • Indexing & Query Performance: Select appropriate index types, including partial and composite indexes, to support common query patterns.
  • Migration Safety Patterns: Write reversible UP/DOWN migrations with guardrails for data safety and operational readiness.

Quick Start

Ask: "Use the database-design skill to propose a PostgreSQL schema for an orders system, including relationships, constraints, and an indexing plan, and provide a safe reversible migration outline."

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 PostgreSQL schema that maintains data integrity under load?

To design a PostgreSQL schema for data integrity, apply appropriate normalization levels, model relationships cleanly, and enforce constraints. This ensures schemas remain correct and performant under load over time.

How do I choose the right indexing strategy for common database query patterns?

To choose the right indexing strategy, select appropriate index types based on your specific query patterns, including partial and composite indexes. This targeted approach ensures reliable query performance for your most common database operations.

How do I write reversible database migrations for schema changes?

To write reversible database migrations, implement safe UP and DOWN migration patterns with built-in guardrails. This approach ensures data safety and operational readiness by allowing schema changes to be cleanly rolled back if issues arise.

When do I need partial or composite indexes in my relational database schema?

You need partial or composite indexes in your relational database schema when specific query patterns require targeted performance optimization. Selecting these index types appropriately supports reliable query execution for complex or filtered database lookups.

Does this database schema design approach work for PostgreSQL-style systems?

Yes, this database schema design approach works directly for PostgreSQL-style systems. It specifically applies normalization guidance, constraint and index design, and reversible migration safety rules tailored to PostgreSQL-style relational database environments.