菜单
Consistent names for Blnk ledgers, @ internal balances, transaction references, and meta_data keys. Use when naming indicators, General Ledger balances, references, ledger titles, or metadata join keys.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Design Blnk Watch risk controls—clean .ws rules, a risk-score rubric, and Watch configuration—via a question-driven workflow. Prefer Blnk Cloud with embedded Watch over self-hosting the Watch binary. Use when writing or reviewing watch scripts, assigning scores or verdicts, consolidating risk outcomes, configuring Cloud Watch / WATCH_SCRIPT_* / ALERT_WEBHOOK_*, or wiring Watch next to Core.
Prepare an application codebase to talk to Blnk Core (latest Core + SDKs, client, env, auth, secrets). Use when wiring Blnk into an existing app, upgrading Blnk versions, adding Blnk config or API keys, enabling secure mode expectations, or checking production readiness. Do not use this skill to implement the install quickstart or a first ledger/transfer demo.
Record Blnk product decisions as numbered markdown files in .blnk_context/. Use when capturing money movement maps, ledger architecture, metadata structure, naming, precision, queueing, or any other Blnk design decision for the team; when starting or updating a Blnk integration context pack.
Turn a product or POC spec into a money movement map plus runnable Blnk app code, tests, and a verified run. Use when the user drops a spec, PRD, or POC doc and wants end-to-end implementation without writing the code themselves.
Root skill for building and implementing on Blnk with recommended best practices. Use whenever the user is designing, integrating, or coding against Blnk Core, Watch, SDKs, or money movement. Load this skill first, then load the child skills it routes to. For a full spec-to-running-app flow, load blnk-implementation.
Design and record Blnk currency exchange with nostro legs, FX spread, and multi-leg or multi-day settlement. Use when converting currencies, building FX or swaps, recording exchange rates or spread, implementing crypto order exchange, or modeling delayed settlement with intermediary balances.
| name | blnk-naming-patterns |
| description | Consistent names for Blnk ledgers, @ internal balances, transaction references, and meta_data keys. Use when naming indicators, General Ledger balances, references, ledger titles, or metadata join keys. |
| metadata | {"author":"blnk","version":"0.1"} |
Fill a naming sheet before creating resources. Pick what you are naming, then open the matching reference.
@ internals, and reference prefixes on the naming sheet below.blnk-ledger-architecture skill for map and layout.meta_data keys are fixed, load the blnk-documentation skill and write .blnk_context/NN_metadata-structure.md (next free number).| Resource | Open |
|---|---|
@ internal / General Ledger balance | references/internal-balances.md |
Transaction reference | references/transaction-references.md |
Ledger title or meta_data keys | references/ledgers-and-metadata.md |
@ prefix for org-owned General Ledger balances.@<Purpose><Currency>_<Source> (for example @WorldUSD_Paypal).@World_Paypal, @WorldUSD, @World).@ rules: references/internal-balances.md.Customer Wallets).meta_data: flat keys only; link related fields with prefixes (order_id, order_sku), never nested objects.intent_stableId[_leg] (not random per retry).Ledgers:
- <Title Case Name>: <what it groups>
Internal balances (@):
- @PurposeCurrency_Source: <purpose>
App balances:
- <alias or meta key> -> balance_id at runtime
Reference prefixes + generator:
- deposit_ | payout_ | hold_ | fx_ | ...
- formula: <intent>_<stable_id>[_<leg>] (deterministic on retry)
meta_data keys (flat, prefixed):
- <prefix_field>: <meaning>
.blnk_context/:
- NN_metadata-structure.md (via documentation skill)