postgresql

Apply structured PostgreSQL best practices for schema design, indexing, and migrations.

9|1|Updated Feb 1, 2026

Search Tags:#performance #indexing #database #postgresql #migrations #sql #schema-design

Ready to run

npx skills add https://github.com/calcosmic/Aether --skill postgresql-calcosmic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postgresql
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/domain/postgresql
Command: npx skills add https://github.com/calcosmic/Aether --skill postgresql-calcosmic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PostgreSQL remains a cornerstone for relational data in many apps, but teams often struggle with inconsistent schemas, brittle migrations, and performance pitfalls. This Skill provides a structured, opinionated guide to standardize database design, indexing strategies, and operational procedures to improve reliability and maintainability.

Core Features & Use Cases

Schema design guidance: normalization, meaningful identifiers, and appropriate data types
Indexing and query optimization: practical rules for when and how to index
Safe migrations and backups: transactionally safe changes and verification steps
Use Case: teams migrating from simpler SQLite or MySQL setups can apply these practices to avoid common PostgreSQL pitfalls

Quick Start

Review your current PostgreSQL setup against these guidelines to identify gaps and suggested improvements.

Frequently Asked Questions about postgresql

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

FAQPage Schema

How do I design a PostgreSQL schema for scalability and reliability?▼

PostgreSQL schema design for scalability relies on normalization, meaningful identifiers, and appropriate data types to enforce structural integrity and improve maintainability.

What is the best way to plan safe PostgreSQL migrations?▼

Safe PostgreSQL migrations require transactionally consistent schema changes and verification steps to prevent data corruption and avoid application downtime during updates.

When do I need indexing for PostgreSQL query optimization?▼

PostgreSQL indexing is needed when query performance degrades, requiring practical rules to determine when and how to apply indexes for optimal database operational tuning.

Can I use these PostgreSQL best practices when migrating from MySQL?▼

These PostgreSQL practices apply directly to teams migrating from simpler SQLite or MySQL setups, helping avoid common reliability and schema pitfalls during the transition.

Why does my PostgreSQL performance degrade after schema migrations?▼

PostgreSQL performance degrades after migrations due to inconsistent schemas and missing indexes, requiring structured versioning and operational tuning to validate applicability.

What are the limitations of applying standard indexing to PostgreSQL?▼

Standard PostgreSQL indexing limitations arise when schema design lacks appropriate data types or normalization, necessitating structured best practices to validate tooling assumptions.