create-assembly-instructions

Files (1)

• SKILL.md

SKILL.md (first lines)

# Create Assembly Instructions

Produce a buildable, ordered guide.

## Inputs

- Project slug → `bom.json`, `wiring.md`, `compatibility.md`, `datasheets/*.md`.

## Structure

Write `<projects_dir>/<slug>/assembly.md`:

### 1. Pre-flight
- Tools required (iron temp, tip, flux, multimeter, logic analyser if needed).
- Workspace prep (ESD considerations).
- Inventory check — confirm all BOM parts are physically present (cross-reference `coverage.md` if it exists).

### 2. Build phases
Order by dependency. Typical phasing:

1. **Bench-power validation** — power the bare MCU first, confirm it boots and is flashable. Don't add peripherals until this passes.
2. **One peripheral at a time** — add, wire, test (smoke test first, then functional test) before moving to the next.
3. **Power rails** — establish 3.3V/5V rails before connecting sensitive parts.
4. **Mechanical / enclosure** — mount only after electrical functions are validated.

For each step include: prerequisites, actions (numbered), test gate ("after this step you should observe X"), rollback if the test fails.

### 3. Common gotchas
Pull the "watch out for" notes from each part's datasheet entry. Highlight ESP32 boot-strapping pin issues, I2C pull-up requirements, decoupling cap placement, etc.

### 4. Final validation
End-to-end functional test plan tied back to the goals in `spec.md`.

## Tone

Imperative, terse, no marketing. Treat the reader as competent but careful — explain the *why* on any non-obvious step (e.g. "leave GPIO0 disconnected until the first flash, otherwise the board won't enter download mode").

From danielrosehill/Claude-Hardware-Spec-Assembly-Plugin, MIT.

More from danielrosehill/Claude-Hardware-Spec-Assembly-Plugin