- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add amplifthq/openmeld --skill postgresql-planning -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add amplifthq/openmeld --skill postgresql-planning -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add amplifthq/openmeld --skill postgresql-planning -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add amplifthq/openmeld --skill postgresql-planning -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/amplifthq/openmeld/tree/HEAD/.agents/skills/postgresql-planningDo publicador
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.
pnpm pg plan to see exact targets and migration checksums. Check
tooling/postgresql/resources.json; a planned name is not a created resource.pg driver; do not build a D1 API emulator or a cross-database
framework. Preserve externally visible IDs and shared schemas.pnpm pg:check for database infrastructure changes. For business work,
add the smallest real PostgreSQL behavior checks for its failure boundary,
then exercise affected consumers. Local infrastructure acceptance is not
proof of cloud connectivity, production scale, or completed business migration.packages/db/postgresql/migrations.
Never convert or edit already-applied D1 history in place. Review generated
SQL for SQLite assumptions, timestamp units, JSON, ordering, conflict behavior,
indexes, constraints and affected query plans.postgres,
broad all-data roles, CREATE, TRUNCATE, role management or migration ledger access.
Tenant authorization remains an explicit owner contract, not a schema name.Use the workflow's migration and cutover checklist rather than copying it here. Check source identity, target identity, immutable migration checksums, lock ownership, runtime grants, restore evidence, mixed-version consumers and one data authority. A completed resource creation is not a completed migration.
Stop the affected operation on a mismatched environment/branch, unknown owner, applied migration drift, failed restore, unresolved production writers, exposed credentials, or missing tenant authorization. After PostgreSQL accepts new business writes, reverting the binding to old D1 would lose data: freeze and reconcile under the recovery plan. New legal agreements and payment/identity challenges require the human. Do not request approval again for already authorized, bounded infrastructure setup.
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
---name: postgresql-planningdescription: Plan and implement OpenMeld PostgreSQL business persistence, schemas and migrations, transactions, Hyperdrive…---# .agents/skills/postgresql-planning/SKILL.mdVisão geral
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.
Perguntas frequentes
Baixe .agents/skills/postgresql-planning/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/amplifthq/openmeld.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.