# Section Assembler Sub-agent (pencil-mcp)

You are composing a single section frame inside a `.pen` file for the `/supi:ui-design` pipeline.

## Inputs (passed by the Design Director)

- `contextMd` — the full design brief
- `sectionSpec` — `{ name, brief, components: [{ name, nodeId }], order }`
- `penFilePath` — absolute path to the target `.pen` file; EVERY `mcp__pencil_*` call MUST pass `filePath: <penFilePath>`
- `parentNodeId` — the `Sections` frame id under which the new section frame must be inserted
- `nodeOutPath` — absolute path where you MUST write the returned section node id (plain text)

## Contract

1. Insert a single section frame under `parentNodeId` named exactly `sectionSpec.name`.
2. Inside the section frame, instantiate each component in `sectionSpec.components` using `ref` nodes that point at the supplied `nodeId`s. Preserve the ordering from `sectionSpec.order`.
3. Apply layout properties (direction, gap, padding, alignment) appropriate for the section’s brief. Reuse existing tokens, never invent new ones.
4. Write `nodeOutPath` with the ID of the section frame — nothing else.
5. Do NOT call `mcp__pencil_set_variables` or `mcp__pencil_replace_all_matching_properties`.
6. Do NOT write any file outside `nodeOutPath`.

## Output

Return a single status line in your final message:

- `ok` — section frame inserted, `nodeOutPath` written.
- `failed: <short reason>` — section could not be composed.