sql-architect

Standardize PostgreSQL 18 database design with UUID v7 keys and forward-only migrations.

3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ralvarezdev/ralvaskills --skill sql-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sql-architect
Source: https://github.com/ralvarezdev/ralvaskills/tree/main/skills/databases/sql-architect
Command: npx skills add https://github.com/ralvarezdev/ralvaskills --skill sql-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database design governance: standardizes SQL practices to reduce defects and improve maintainability across schemas.

Core Features & Use Cases

  • Schema design rules: primary keys, foreign keys, NOT NULL, CHECK constraints, audit columns, soft delete.
  • Naming conventions: tables, columns, FKs, indexes, constraints, sequences.
  • Indexing strategy: index all FK columns, use appropriate index types, partial indexes for soft-deletes.
  • Query patterns: parameter binding, explicit column lists, RETURNING, upserts, cursor-based pagination, CTEs.
  • Migrations & security: forward-only migrations, role-based access, RLS; security guidelines.
  • Performance & JSON: EXPLAIN ANALYZE, performance tuning, JSON guidance.
  • Engine-specific notes: PostgreSQL 18 primary; MySQL 9 and SQLite 3.53 notes.

Quick Start

Initialize your project with UUID v7 primary keys, NOT NULL and CHECK constraints, soft delete via deleted_at, and forward-only migrations to enforce a scalable schema.

Frequently Asked Questions about sql-architect

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

FAQPage Schema
How do I enforce UUID v7 primary keys and consistent naming in PostgreSQL schema design?

PostgreSQL schema design enforces UUID v7 primary keys, consistent naming, NOT NULL constraints, and audit columns to standardize database governance and reduce defects across scalable schemas.

What's the best way to handle forward-only migrations and soft deletes in PostgreSQL?

Forward-only migrations and soft deletes in PostgreSQL use a deleted_at column with partial indexes, ensuring safe schema evolution and maintaining data integrity without destructive rollback operations.

How do I prevent N+1 query problems and optimize indexing strategies in PostgreSQL?

Optimizing indexing strategies in PostgreSQL requires indexing all foreign key columns, using appropriate index types, and applying partial indexes for soft-deletes to prevent N+1 query problems and improve performance.

Does this database design approach work with MySQL 9 and SQLite 3.53, or is it PostgreSQL only?

This database design approach targets PostgreSQL 18 as the primary engine but includes specific compatibility notes for MySQL 9 and SQLite 3.53 to support cross-engine maintainability.

How do I apply role-based access control and row-level security in PostgreSQL migrations?

PostgreSQL migrations apply role-based access control and row-level security (RLS) to enforce security governance, ensuring scalable databases maintain strict access boundaries during forward-only schema changes.

When should I use cursor-based pagination and CTEs over traditional offset pagination in PostgreSQL?

Cursor-based pagination and CTEs in PostgreSQL replace traditional offset pagination to support scalable query patterns, using explicit parameter binding and RETURNING clauses for maintainable performance.