| name | masm-constants |
| description | Enforce constant definition and organization conventions for Miden Assembly (.masm) files. Use when editing, reviewing, or creating .masm files that define or use constants. |
MASM Constant Conventions
Placement
Constants must be defined at the top of the file, before any procedure definitions, but after imports or type aliases.
Organization
Constants Section (first)
Group non-error constants by topic. Use blank lines between sections. Common topics:
- Slot names – use
word("path::to::slot") for slot identifiers
- Memory pointer offsets – offsets into memory regions
- Magic numbers / values – domain-specific literals
- Event identifiers – for
emit / trace
Order sections by dependency or by usage frequency. Put the most widely used first.
Errors Section (after constants)
Errors (panic/assert error codes, e.g. ERR_*) go in a dedicated "errors" section, placed after the constants section. Define them with string values describing the error.
Naming
Memory Pointers
Memory pointer constants describe offsets into memory regions that are shared or global (e.g. layout of a memory region, input/output structure offsets). They are not scoped to a single procedure and do not use the procedure prefix.
# Good: descriptive, shared usage
const ASSET_OFF = 0
const AMOUNT_OFF = 1
const NOTE_DATA_LEN = 16
# Or grouped by memory region if applicable
const INPUT_PTR_OFF = 0
const INPUT_LEN_OFF = 1
Memory Locals Offsets
Memory locals offsets are procedure-scoped: they describe offsets within a procedure's local memory. They must be they belong to:
