# Standalone Sample and Recipe Modules

Listen Step 2.63.0 or newer accepts these packages through the existing JSON import action under Modules. The common format is `listen-step-protocol@1`; set `kind` to `sample` or `recipe`. Protocol and Step package behavior remains unchanged. Examples are in `../assets/`.

## Sample

- Required: `name`, `kind: "sample"`, and `plate: {"type": ...}`. Supported plate types are `96-well` (A1-H12), `48-cell` (A1-F8), `24-cell` (A1-D6), `12-well` (A1-C4), and `8-strip` (A1-A8). `plateType` is also accepted.
- `cells` is an optional object keyed by well name; each populated entry has `used: true` (or omitted), optional string `sampleName`, and optional string `sampleAmount` including its unit. Out-of-range wells fail the entire import. Empty wells should be omitted.
- Optional `recipeSnapshots` maps snapshot keys to `{recipeId, name, tables, materials}`. A cell may reference a snapshot with `recipeKey`, an optional matching `recipeId`, and optional `recipeColor` (`green`, `blue`, `yellow`, `purple`, or `orange`). The snapshot is embedded; do not assume it creates or tracks a standalone Recipe. Every assignment must reference an included snapshot.
- Importing photo file paths is not supported. Add photos in Listen Step; do not put private local paths or fabricated images into a package.

## Recipe

- Required: `name`, `kind: "recipe"`, and at least one `tables` entry. Each table has string-array `header`, `rows` of string arrays of the same width, optional `name`, and optional unique string `id`. `materials` can contain `{name, detail}` objects. Preserve units explicitly.
- Optional table alternatives use the same `branchGroup` string on multiple tables, with unique IDs; `tableChoices` maps the group to a selected table ID. Optional `parameterBranches` use `{id, row, column, options: [{id, value}, ...], selected}`. The selected option must equal the referenced table cell. Indexes are zero-based. Include at least two options, and do not fabricate branches.
- `tags` is an optional array of strings for either module. Unknown metadata, local photos and external file contents are not promised to survive. Verify resulting modules in the target app; imported items get new IDs and do not overwrite existing modules.
