メニュー
PostgreSQL convention lens consulted BEFORE writing schema/migrations — indexing, constraints, row-level security, and timestamp/type hygiene. Appended to impl-conventions.txt by the stack-conventions pack. Also usable standalone.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when executing implementation plans with independent tasks in the current session
Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.
Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.
Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.
| name | postgres-conventions |
| description | PostgreSQL convention lens consulted BEFORE writing schema/migrations — indexing, constraints, row-level security, and timestamp/type hygiene. Appended to impl-conventions.txt by the stack-conventions pack. Also usable standalone. |
When: consulted by plan-writer when the plan adds a table, column, index, or migration, and by implement-feature while writing the schema/migration, in projects where the stack-conventions pack is installed. Complements the migration-safety review lens (that catches unsafe change shapes after the fact; this shapes the schema up front).
Scope: schema and migration the change introduces. Advisory knowledge, makes no edits.
bigint generated always as identity, or uuid) unless a natural key is truly stable. Foreign keys carry an explicit references + on delete policy — never leave the cascade behaviour implicit.unique index for any real uniqueness invariant (don't enforce it only in app code). Name indexes predictably (idx_<table>_<cols>).alter table … enable row level security) and write policies keyed on the tenant/owner column. Whitelist the allowed principal (policy using (tenant_id = current_tenant())) — never a deny-list of bad actors. RLS is enforcement, not a substitute for authorization checks in the app; it is the backstop when a query forgets one.not null, check, unique, and FK constraints encode invariants where they cannot be bypassed. If a rule matters, the DB should hold it too.timestamptz (never bare timestamp) for instants; store UTC. text over varchar(n) unless a length limit is a real domain rule. numeric for money, never float. Enums via a lookup table or PG enum — not free-form strings.set not null; never a bare not null add on a populated table. One logical change per migration.plan-writer: record indexes, constraints, RLS policies, and the code↔snake_case mapping (see naming-conventions) in Decisões Técnicas, not left to implement-time guesswork.implement-feature: match the existing migration tool and file convention already in the repo before writing a new migration.