atomic-fi

Onboard a country's compliance regime — adds sanctions lists to Watchman, creates ZenRule rules for that jurisdiction, generates test corpus, and suggests Lotus probes. Use whenever the user wants to "add a country", "onboard India/France/UAE", "set up compliance for country X", or any phrasing that maps a country to sanctions lists + rules + test data.

Populates the DB with 100 AH / 1k CP / 10k transactions, runs all rules sequentially, prints per-rule rollup, and suggests Lotus probes. Use whenever the user wants to "run the master suite", "test all rules", "run 10k transactions", "populate the DB for the demo", "seed for Lotus", or any phrasing that requests a full compliance correctness + scale run. Composes existing mix tasks — never auto-commits.

Authors a complete vertical slice (JDM rule + NDJSON corpus + proof.md) for a single use-cases.md row OR a regulation snippet (PDF/text) — for the atomic-fi ZenRule engine and corpus.validate write path. Use whenever the user wants to "add a scenario", "ship use-case

Turns a list of regulation URLs into per-rule proofs (JDM rule + NDJSON corpus + proof.md) and combines them into a single regulator-readable master.md. Use whenever the user wants to "prove these regulations", "generate rules from URLs", "build proofs for CFR/USC/PDF links", or any phrasing that maps multiple regulation sources to end-to-end deterministic proofs. Orchestrates scenario-author and corpus-from-rule per URL, then concatenates all proofs into benchmarks/correctness/master.md. Never auto-commits.

Authors and verifies JDM (JSON Decision Model) rule files for the atomic-fi ZenRule engine from English-language requirements. Use whenever the user wants to write, edit, or test a compliance / payment-rules decision — including phrases like "add a rule", "create a ruleset", "write a KYC check", "block stablecoin", "de minimis", "limit transactions when X", "compliance gap", "GENIUS Act", "BSA §326", "OFAC screening rule", or any change that should land in `priv/zenrule/<rule_type>/`. The skill grounds itself in the real `AtomicFi.RuleEngine.Payload` schema, generates the JDM JSON directly under the correct rule-type subdirectory, builds test contexts from the rule's input columns, iteratively tests against the live ZenRule agent via curl, and amends the rule until all tests pass or escalates after a soft cap. Saved rules immediately surface in the JDM editor at `http://localhost:5173/rules/<rule_type>` after a browser refresh (the agent picks the file up within ~5s of the write).

Given a scenario slug, generates a Bruno .bru collection folder and CI-runs it with `bru run` to confirm all assertions pass. Use whenever the user wants to "generate Bruno tests for a scenario", "create .bru files for slug", "turn this corpus into a Bruno collection", or any phrasing that maps a corpus/zen_rules scenario to a runnable Bruno folder. One slug in, one green folder out. Never auto-commits.

Generates a deterministic test corpus for a ZenRule JDM rule and verifies it against the live atomic-fi write path. Use whenever the user wants to "build fixtures for de_minimis", "generate test data for the SDN rule", "make a corpus for transaction-screening/X", "trust-but-verify this rule", or any phrasing that asks for synthetic payloads paired with expected rule-engine responses. The skill authors four NDJSON files (account_holders, counterparties, payment_accounts, transactions) under `corpus/zen_rules/<rule_corpus>/`, invokes `mix corpus.validate` which inserts each row through the production contexts and creates the transaction (running the full RuleEngine path), then diffs the resulting `%Transaction{}` state against each row's inline `_expected` block. Iterates until convergence.

Author and extend broad regression vitest E2E tests against the AtomicFi API using a typed SDK generated from the OpenAPI spec via `@hey-api/openapi-ts`. Distinct from `usecase-vitest` (5 demo use-cases with recordings) — this skill covers full-API resource CRUD + RLS isolation + screening fixtures and runs against multiple environments. Use when scaffolding or extending E2E coverage for one or more controllers in `lib/atomic_fi_api/controllers/`.

Human-led API session that authors and debugs a vitest integration test for one of the 5 fixed AtomicFi use-cases, then optionally fans out to MDX (Docusaurus cookbook) and Bruno (collection) generator agents in parallel. Triple purpose — QA pass, in-session bug fixing, and demo-ready output. Use when the user wants to walk through `setup-platform`, `onboard`, `transact`, `respond-to-aml-document-request`, or `add-documents`.