How does this skill manage database transactions?

It enforces a convention where methods starting transactions use a 'TX_' prefix and handles the separation between methods that create transactions and those that merely participate in them.

Does it support financial data handling?

Yes, it mandates the use of exact numeric/decimal types (e.g., numeric(19, 4)) for monetary values to prevent the accumulation of rounding errors found in floating-point types.

Why does this skill recommend ULIDs over standard UUIDs or serials?

It defaults to ULID stored as UUID to prevent ID enumeration attacks while remaining time-sortable for high indexing efficiency.

How is type safety enforced for JSONB columns?

The skill requires that all JSONB columns be typed in the ORM or schema immediately, preventing runtime errors caused by accessing undefined properties.

PostgreSQL Development Patterns

Name: PostgreSQL Development Patterns
Author: pbdeuchler

bypbdeuchler

Gestión de Bases de Datos

Enforces production-grade PostgreSQL standards for transaction safety, strict typing, and consistent naming to prevent data corruption.

Acerca de

This skill equips Claude with a rigorous framework for building and maintaining robust PostgreSQL database layers. It streamlines development by enforcing transaction safety through specific naming conventions, ensuring type safety for identifiers and JSONB columns, and maintaining strict read-write separation. Ideal for developers building financial systems or high-scale applications, it helps prevent common pitfalls such as floating-point errors, ID enumeration attacks, and accidental mutations in read-only contexts.

Características Principales

Enforced transaction safety via the TX_ naming convention
Strict read-write client separation at the compile-time type level
Exact decimal handling for financial data to eliminate rounding errors
Type-safe ULID primary key implementation to prevent ID enumeration
Standardized snake_case naming for all database identifiers
0 GitHub stars

Casos de Uso

Designing secure and performant database schemas for multi-tenant applications
Standardizing database access patterns and migrations across engineering teams
Implementing complex transaction logic in backend services with zero data corruption

Acerca de

Características Principales

Enforced transaction safety via the TX_ naming convention
Strict read-write client separation at the compile-time type level
Exact decimal handling for financial data to eliminate rounding errors
Type-safe ULID primary key implementation to prevent ID enumeration
Standardized snake_case naming for all database identifiers
0 GitHub stars

Casos de Uso

Designing secure and performant database schemas for multi-tenant applications
Standardizing database access patterns and migrations across engineering teams
Implementing complex transaction logic in backend services with zero data corruption