Menu
Use when a Rust or MASM test needs to construct an account, note, transaction, or other domain object — build it with the existing test fixtures.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | use-test-fixtures |
| description | Use when a Rust or MASM test needs to construct an account, note, transaction, or other domain object — build it with the existing test fixtures. |
When a test needs a domain object, reach for the existing fixture infrastructure:
NoteBuilder.ScriptBuilder.AccountIdBuilder (or the existing ACCOUNT_ID_* constants).rand_value() (deterministic seed-driven RNG).AccountBuilder with the testing feature.Don't write a new AccountId::dummy(...), Note::test_only(...), or one-off random helper. If the existing fixtures can't express what you need, extend them — don't fork.
Shared fixtures encode the domain's validation rules, so a fixture-built object has the right bits and survives serialization; a hand-rolled dummy() usually doesn't, letting tests pass against invariants the real code never enforces. Reusing fixtures also lets one upgrade propagate to every test.
// Good
let note = NoteBuilder::new()
.recipient(test_recipient())
.with_asset(rand_value())
.build()?;
let account_id = AccountIdBuilder::new().build();
// Bad
let note = Note {
metadata: NoteMetadata::default(),
inputs: NoteInputs::default(),
assets: NoteAssets::default(),
recipient: NoteRecipient::dummy(),
};
let account_id = AccountId::try_from(Word::default()).unwrap();
Enforce type-signature conventions for public Miden Assembly (.masm) procedures. Use when adding, editing, or reviewing a `pub proc` signature — parameter and return types, semantic type aliases, struct/array/tuple types, and how the signature maps onto the operand stack and the doc-comment Inputs/Outputs.
Enforce inline commenting conventions for Miden Assembly (.masm) files. Use when editing, reviewing, or creating .masm files.
Enforce doc comment conventions for Miden Assembly (.masm) procedures. Use when editing, reviewing, or creating .masm procedures, especially when documenting inputs, outputs, panic conditions, or invocation types.
Use when writing kernel, account, or note MASM code that reads from or writes to the advice provider (advice stack / advice map) — validate advice data.
Use when writing a Rust test that exercises a failure path or a MASM test that expects a `panic` / `assert` — assert on the specific expected error variant or error code.
Use when writing or reviewing MASM hot paths — prefer the cheaper equivalent instruction: `neq.0` over `gt.0` for non-zero checks, `cdrop` over an `if/else` selecting between two values, `dup.N` over `loc_load` for a value still on the stack, `eqw` over element-wise word comparison, `u32gt`/`u32lt` over generic `gt`/`lt` on known-u32 operands.