- 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.
FAQ
게시자에게서 .agents/skills/postgresql-planning/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/amplifthq/openmeld에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.