القائمة
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.
التثبيت باستخدام 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.
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.
Enforce conventions for the IndexedDB/Dexie persistence layer of the Miden web client, which lives in the web-sdk repo (idxdb-store crate). Use when editing TypeScript in `crates/idxdb-store/src/ts/`, writing Dexie transactions, or modifying the database schema.
| name | felt-construction |
| description | 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. |
Do not call Felt::new_unchecked(x) when x could be greater than or equal to the field order. new_unchecked stores any u64 raw without reduction, so an out-of-range value produces a non-canonical Felt that no longer equals the original input on a canonical comparison — a classic source of hard-to-attribute bugs.
Use one of:
Felt::from(x) where x is a u32, u16, or u8 (infallible).Felt::new(x) or Felt::try_from(x) for u64 inputs — both are checked and return Result<Felt, FeltFromIntError>, rejecting values that are >= Felt::ORDER.If you have independently proven the bound and need the unchecked path, only then reach for Felt::new_unchecked(x), comparing against Felt::ORDER (the u64 field order; there is no Felt::MODULUS).
The field order sits just below 2^64 (2^64 - 2^32 + 1), so an out-of-range u64 is reduced only for a narrow band of large values — most tests pass and production hits the bad input as a value mismatch far from the call. Felt::from(u32) cannot exceed the field, and Felt::new / Felt::try_from force the bound check and surface overflow as a FeltFromIntError.
// Good: u32 input, infallible conversion
let f = Felt::from(slot_index as u32);
// Good: untrusted u64 input, checked conversion
let f = Felt::try_from(user_value).map_err(|_| Error::FeltOverflow)?;
// Good: equivalent checked constructor
let f = Felt::new(user_value).map_err(|_| Error::FeltOverflow)?;
// Bad: stores any u64 raw with no reduction; a value >= Felt::ORDER
// yields a non-canonical Felt that does not equal user_value
let f = Felt::new_unchecked(user_value);