# Postgresql Planning

Plan and implement OpenMeld PostgreSQL business persistence, schemas and migrations...

- Repository: https://github.com/amplifthq/openmeld (1404 stars)
- Category: Data and ML
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add amplifthq/openmeld --skill postgresql-planning -g -a claude-code -y`
Codex: `npx skills add amplifthq/openmeld --skill postgresql-planning -g -a codex -y`
Cursor: `npx skills add amplifthq/openmeld --skill postgresql-planning -g -a cursor -y`
Gemini CLI: `npx skills add amplifthq/openmeld --skill postgresql-planning -g -a gemini-cli -y`

## Description

Plan and implement OpenMeld PostgreSQL business persistence, schemas and migrations, transactions, Hyperdrive access, and data cutover. Use for the shared relational database transition or PostgreSQL work; not for unrelated D1 performance fixes or OpenConnector's upstream database.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# OpenMeld PostgreSQL Planning

All OpenMeld databases belong to the **Amplift** PlanetScale organization
(`amplift`), never the operator's personal organization. Pass `--org amplift`
explicitly; login defaults are not the resource owner.

The architecture is decided: Cloudflare Hyperdrive connects Workers to
PlanetScale PostgreSQL. Start from current source, not a new vendor comparison
or the superseded D1 capacity threshold. Production has used PostgreSQL since
the 2026-10-04 cutover. Shared staging reuses `openmeld-postgresql-stg` through
its own Hyperdrive binding and the guarded `pnpm staging:deploy` workflow.
The former staging D1 database is retained for historical test-data inspection.
Use standard PlanetScale Postgres for this foundation. Neki preview enrollment
does not change the chosen engine or authorize a sharded database migration.
The staging/local baseline is PostgreSQL 18 at the latest supported stable minor.
Use older versions only for a demonstrated compatibility constraint.
Production capacity changes require measured demand. Keep capacity stable while
isolating code-path regressions; use the current workflow's metrics and query
plans before recommending a larger machine.

## Shortest useful start

The rest: https://github.com/amplifthq/openmeld/blob/HEAD/.agents/skills/postgresql-planning/SKILL.md