- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add amplifthq/openmeld --skill postgresql-planning -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add amplifthq/openmeld --skill postgresql-planning -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add amplifthq/openmeld --skill postgresql-planning -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add amplifthq/openmeld --skill postgresql-planning -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/amplifthq/openmeld/tree/HEAD/.agents/skills/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.
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.md總覽
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.
常見問題
從發布者下載 .agents/skills/postgresql-planning/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/amplifthq/openmeld。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。