Menu
Use when writing or reviewing code that posts, holds, voids, reverses, or reconciles money movements - double-entry postings, wallet balances, idempotency keys, FX conversion, or Blnk / pgledger integration.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | ledger |
| description | Use when writing or reviewing code that posts, holds, voids, reverses, or reconciles money movements - double-entry postings, wallet balances, idempotency keys, FX conversion, or Blnk / pgledger integration. |
SUM(debits) == SUM(credits) per currency.<domain>:<operation>:<business-id>, linked to all of its postings. Retries reuse the same key.materialized_balance == account-type normal-balance signed SUM(postings) - the reconciliation queries in the references must return zero rows.Detect which ledger backs the service from its dependencies/config, then read the matching reference before writing code:
references/blnk-api-contract.md - hold/inflight semantics, available = balance - inflight, timeout means PENDING_RECONCILIATION, and duplicate references are accepted only after the original operation is fetched and matched.references/pgledger-invariants.md - schema law (append-only trigger, balance_after), sorted FOR UPDATE locking, zero-row verification queries.Schema changes to ledger tables follow the migrations skill (append-only trigger stays, no destructive ops).
Use when reviewing code, a diff, a module, an architecture, or a design/spec document against house standards - including multi-expert panel reviews ("review with a DDD expert and an asset-finance expert"). Also when running a removal-first simplification sweep: "what can we remove", "product simplification review".
Use when executing an implementation plan or building a scoped feature or fix - after scope is clear, before code gets written. Triggers on "implement the plan at PATH", "start slice SP-2b".
Use when investigating any bug, error, crash, stack trace, failing or flaky test, incident, regression, unexpected behavior, or "why is this happening" question - before proposing or applying a fix.
Use when an implementation needs proof against the live running stack: after build completes, before ship, or when asked to verify, e2e-test, smoke-test, or demo that an API, UI, or DB change actually works.
Use when building or styling sportsbook, betting, or casino (iGaming) interfaces: odds displays, betslips, live-event states, suspended markets, casino game grids, or wallet and money surfaces.
Use when creating or reviewing database migrations - Liquibase or Flyway, new tables, columns, indexes, constraints, backfills, or any DDL against Postgres.