replace-with-skill-namelisted

# <Vendor> <Board> (<MCU>) <One paragraph: what this board is, and what the reference files hold. Say explicitly that the detail lives in the reference files and should be read rather than guessed at.> - `reference/board-hardware.md` — <what it answers> - `reference/recipes.md` — <what it answers> - `template/` — a complete working project that builds and flashes, plus a scaffolding script. ## Orientation | | | |---|---| | MCU | <part number, core, flash, RAM, package> | | Clocks | <crystals populated, and the clock tree that is known to work> | | Display | <controller, resolution, bus, pins> | | LED / button | <pin and **polarity** for each> | | Storage | <internal / external flash, SD, PSRAM, with addresses> | | USB | <peripheral, pins, bootloader behaviour> | | Debug | <SWD/JTAG/UART header and pins> | <Delete rows that don't apply; add rows the board needs.> ## Rules that prevent the expensive mistakes <10–15 numbered rules from your bring-up log. Each is imperative and carries its consequence. Template for one entry:> 1. **`<the setting, in code form>`** — <why the board needs it>. Without it, <the symptom, which should not obviously point back at this setting>. ## When the task is <the thing this board is used for> <The one or two areas where the naive approach is badly wrong. Give the mechanism and the numbers, so the model can generalise past the case you wrote down. Delete if the board has none.> ## Starting a new project Do not hand-assemble one. `tem