القائمة
Use when changing a numeric or string constant in Rust or MASM that has a counterpart on the other side — keep the two definitions from drifting apart.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 or reviewing MASM hot paths — prefer the cheaper equivalent instruction: `neq.0` over `push.0 gt` 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 hand-rolled element-wise word comparison, `u32gt`/`u32lt` over generic `gt`/`lt` on known-u32 operands.
Use when writing a GENERIC MASM storage utility (one that operates over a caller-chosen slot or map) inside a reusable account component — receive the slot id as a parameter so the utility works against any slot, not one hard-coded one.
Use when constructing a `Felt` from a numeric value in Rust — avoid silently producing a non-canonical Felt that no longer equals the original input.
Critical pitfalls and safety rules for Miden frontend development. Covers WASM initialization, concurrent access crashes, COOP/COEP headers, BigInt handling, Bech32 network mismatches, IndexedDB state loss, auto-sync side effects, Vite configuration, and React rendering race conditions. Use when reviewing, debugging, or writing Miden frontend code.
Guide for advanced Miden frontend development using source repo exploration. Covers AI development practices (Plan Mode, verification-driven development, context engineering, sub-agents) and maps the Miden web-sdk source repository for discovering advanced patterns. Use when building complex applications beyond basic hook usage, implementing custom signers, working with WasmWebClient directly, or troubleshooting SDK internals.
| name | masm-rust-constant-parity |
| description | Use when changing a numeric or string constant in Rust or MASM that has a counterpart on the other side — keep the two definitions from drifting apart. |
Constants that exist on both the MASM and the Rust side must not drift. Prefer a single source of truth: define the constant in MASM and generate the Rust counterpart from it, rather than hand-maintaining the same literal in two places.
This repo already does that in crates/miden-protocol/build.rs: it scans the MASM sources for const ERR_... = "..." and const X = event("...") definitions and emits Rust files (tx_kernel_errors.rs, protocol_errors.rs, transaction_events.rs) that are pulled in with include!(concat!(env!("OUT_DIR"), ...)) (see src/errors/mod.rs and src/transaction/kernel/tx_event_id.rs). A new error or event constant added in MASM gets its Rust binding automatically.
For constants not covered by codegen (memory offsets, capacity limits, field widths still duplicated in src/constants.rs and src/transaction/kernel/memory.rs, mirroring asm/kernels/transaction/lib/memory.masm), update both sides in the same PR — and prefer extending the generation over adding another hand-copied literal.
The kernel reads memory at offsets the Rust host wrote. If one side changes ACTIVE_INPUT_NOTE_PTR and the other doesn't, every transaction misreads its state, and the bug stays invisible until a value happens to straddle the changed offset. Generating one side from the other removes the chance to forget.
Source of truth in MASM:
const ERR_PROLOGUE_NEW_ACCOUNT_VAULT_MUST_BE_EMPTY="new account must have an empty vault"
Generated into OUT_DIR by build.rs and included via include!(concat!(env!("OUT_DIR"), "/tx_kernel_errors.rs")):
pub const ERR_PROLOGUE_NEW_ACCOUNT_VAULT_MUST_BE_EMPTY: MasmError =
MasmError::from_static_str("new account must have an empty vault");
For a constant that is still hand-duplicated, change both in the same PR:
// crates/miden-protocol/src/constants.rs
pub const MAX_INPUT_NOTES_PER_TX: usize = 1024;
# crates/miden-protocol/asm/kernels/transaction/lib/constants.masm — must equal the Rust constant
pub const MAX_INPUT_NOTES_PER_TX = 1024