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.
Mental model and workflows for Blnk inflight transactions when other work must finish before a movement is complete. Use when authorizing then capturing, escrow holds, commit or void inflight, inflight expiry, split inflight, or bulk commit/void.
Investigate product intent and design Blnk money movement maps (including maps-tool JSON) and ledger architecture before coding balances and transactions. Use when structuring ledgers, discovering reporting needs or connected tools, drawing fund flows, exporting map.blnkfinance.com JSON, grouping balances into ledgers, or planning General Ledger @ balances.