Govcraft

Design and write idiomatic acton-reactive (9.x) actor systems in Rust. Use this whenever you are writing, reviewing, or planning code that uses acton-reactive, and also whenever a Rust async design starts reaching for Arc<Mutex<T>>, RwLock, shared mutable state across tasks, hand-rolled worker pools, retry/restart loops, or an orchestrator function that drives other tasks. Use it before writing the first actor, not after, because the expensive mistakes are architectural. Also use it when the user mentions actors, message passing, event-driven or reactive architecture, supervision, pub/sub brokers, or asks why their async Rust deadlocks.

This skill should be used when interacting with the beankeeper accounting system via the `bk` CLI. Use when the user asks to "record a transaction", "post an entry", "check a balance", "generate a report", "create a company", "set up accounts", "import bank statements", "set a budget", "compare budget vs actual", "reconcile entries", "verify the ledger", "export data", "attach a receipt", or any financial bookkeeping task. Also use when piping structured JSON output from `bk` into other tools or agents.

Use when writing, creating, editing, or reviewing SchemaForge .schema files. Use when defining data models, entity schemas, field types (incl. `duration`, `bytes`, and `map<text, V>`), relations, access control, or multi-tenant hierarchies in the SchemaForge DSL syntax. Use when declaring write-time validation, computed fields, or computed defaults via the CEL rule annotations `@require` / `@compute` / `@default` (in-process, fail-closed, no gRPC), including single-hop cross-entity reads (`related.<field>.<col>`) inside `@require`. Use when declaring `unique` field constraints (per-tenant for `@tenant(...)` schemas, table-wide otherwise) and handling the 409 `unique_violation` error path. Use when declaring `file` fields backed by S3-compatible storage (MinIO, AWS S3, R2, Wasabi), configuring `[schema_forge.storage]` backends, or wiring upload/download/scan flows. Use when scaffolding or regenerating the React site with `schema-forge site generate`, wiring the `/app/*` per-entity pages or the runtime-dynamic