القائمة
Use when writing or editing a Rust error message, panic/assert string, or MASM `ERR_*` constant — follow the Rust convention for error-message casing and punctuation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | lowercase-error-messages |
| description | Use when writing or editing a Rust error message, panic/assert string, or MASM `ERR_*` constant — follow the Rust convention for error-message casing and punctuation. |
Error messages (in Error enum #[error("...")] attributes, panic!, assert! messages, MASM ERR_* constant strings) follow Rust's convention:
Examples of correct shape: "invalid account id length", "note not found", "failed to deserialize storage".
Error messages get composed into chains and contexts, where a capital letter or trailing period mid-chain makes them read like disconnected sentences. Lowercase-with-no-punctuation is the convention std, thiserror, and most crates already follow.
// Good
#[derive(Debug, thiserror::Error)]
pub enum AccountError {
#[error("invalid account id length, expected {expected} bytes, got {got}")]
InvalidLength { expected: usize, got: usize },
#[error("account not found")]
NotFound,
}
// Bad
#[derive(Debug, thiserror::Error)]
pub enum AccountError {
#[error("Invalid account id length: expected {expected} bytes, got {got}.")]
InvalidLength { ... },
#[error("Account not found!")]
NotFound,
}
# Good
const ERR_NOTE_NOT_FOUND = "note not found"
# Bad
const ERR_NOTE_NOT_FOUND = "Note not found!"
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.